'\" t
.\"     Title: git-config
.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\"      Date: 08/19/2015
.\"    Manual: Git Manual
.\"    Source: Git 2.5.0.400.gff86faf
.\"  Language: English
.\"
.TH "GIT\-CONFIG" "1" "08/19/2015" "Git 2\&.5\&.0\&.400\&.gff86faf" "Git Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
git-config \- Get and set repository or global options
.SH "SYNOPSIS"
.sp
.nf
\fIgit config\fR [<file\-option>] [type] [\-z|\-\-null] name [value [value_regex]]
\fIgit config\fR [<file\-option>] [type] \-\-add name value
\fIgit config\fR [<file\-option>] [type] \-\-replace\-all name value [value_regex]
\fIgit config\fR [<file\-option>] [type] [\-z|\-\-null] \-\-get name [value_regex]
\fIgit config\fR [<file\-option>] [type] [\-z|\-\-null] \-\-get\-all name [value_regex]
\fIgit config\fR [<file\-option>] [type] [\-z|\-\-null] \-\-get\-regexp name_regex [value_regex]
\fIgit config\fR [<file\-option>] [type] [\-z|\-\-null] \-\-get\-urlmatch name URL
\fIgit config\fR [<file\-option>] \-\-unset name [value_regex]
\fIgit config\fR [<file\-option>] \-\-unset\-all name [value_regex]
\fIgit config\fR [<file\-option>] \-\-rename\-section old_name new_name
\fIgit config\fR [<file\-option>] \-\-remove\-section name
\fIgit config\fR [<file\-option>] [\-z|\-\-null] \-l | \-\-list
\fIgit config\fR [<file\-option>] \-\-get\-color name [default]
\fIgit config\fR [<file\-option>] \-\-get\-colorbool name [stdout\-is\-tty]
\fIgit config\fR [<file\-option>] \-e | \-\-edit
.fi
.sp
.SH "DESCRIPTION"
.sp
You can query/set/replace/unset options with this command\&. The name is actually the section and the key separated by a dot, and the value will be escaped\&.
.sp
Multiple lines can be added to an option by using the \fI\-\-add\fR option\&. If you want to update or unset an option which can occur on multiple lines, a POSIX regexp value_regex needs to be given\&. Only the existing values that match the regexp are updated or unset\&. If you want to handle the lines that do \fBnot\fR match the regex, just prepend a single exclamation mark in front (see also the section called \(lqEXAMPLES\(rq)\&.
.sp
The type specifier can be either \fI\-\-int\fR or \fI\-\-bool\fR, to make \fIgit config\fR ensure that the variable(s) are of the given type and convert the value to the canonical form (simple decimal number for int, a "true" or "false" string for bool), or \fI\-\-path\fR, which does some path expansion (see \fI\-\-path\fR below)\&. If no type specifier is passed, no checks or transformations are performed on the value\&.
.sp
When reading, the values are read from the system, global and repository local configuration files by default, and options \fI\-\-system\fR, \fI\-\-global\fR, \fI\-\-local\fR and \fI\-\-file <filename>\fR can be used to tell the command to read from only that location (see the section called \(lqFILES\(rq)\&.
.sp
When writing, the new value is written to the repository local configuration file by default, and options \fI\-\-system\fR, \fI\-\-global\fR, \fI\-\-file <filename>\fR can be used to tell the command to write to that location (you can say \fI\-\-local\fR but that is the default)\&.
.sp
This command will fail with non\-zero status upon error\&. Some exit codes are:
.sp
.RS 4
.ie n \{\
\h'-04' 1.\h'+01'\c
.\}
.el \{\
.sp -1
.IP "  1." 4.2
.\}
The config file is invalid (ret=3),
.RE
.sp
.RS 4
.ie n \{\
\h'-04' 2.\h'+01'\c
.\}
.el \{\
.sp -1
.IP "  2." 4.2
.\}
can not write to the config file (ret=4),
.RE
.sp
.RS 4
.ie n \{\
\h'-04' 3.\h'+01'\c
.\}
.el \{\
.sp -1
.IP "  3." 4.2
.\}
no section or name was provided (ret=2),
.RE
.sp
.RS 4
.ie n \{\
\h'-04' 4.\h'+01'\c
.\}
.el \{\
.sp -1
.IP "  4." 4.2
.\}
the section or key is invalid (ret=1),
.RE
.sp
.RS 4
.ie n \{\
\h'-04' 5.\h'+01'\c
.\}
.el \{\
.sp -1
.IP "  5." 4.2
.\}
you try to unset an option which does not exist (ret=5),
.RE
.sp
.RS 4
.ie n \{\
\h'-04' 6.\h'+01'\c
.\}
.el \{\
.sp -1
.IP "  6." 4.2
.\}
you try to unset/set an option for which multiple lines match (ret=5), or
.RE
.sp
.RS 4
.ie n \{\
\h'-04' 7.\h'+01'\c
.\}
.el \{\
.sp -1
.IP "  7." 4.2
.\}
you try to use an invalid regexp (ret=6)\&.
.RE
.sp
On success, the command returns the exit code 0\&.
.SH "OPTIONS"
.PP
\-\-replace\-all
.RS 4
Default behavior is to replace at most one line\&. This replaces all lines matching the key (and optionally the value_regex)\&.
.RE
.PP
\-\-add
.RS 4
Adds a new line to the option without altering any existing values\&. This is the same as providing
\fI^$\fR
as the value_regex in
\-\-replace\-all\&.
.RE
.PP
\-\-get
.RS 4
Get the value for a given key (optionally filtered by a regex matching the value)\&. Returns error code 1 if the key was not found and the last value if multiple key values were found\&.
.RE
.PP
\-\-get\-all
.RS 4
Like get, but does not fail if the number of values for the key is not exactly one\&.
.RE
.PP
\-\-get\-regexp
.RS 4
Like \-\-get\-all, but interprets the name as a regular expression and writes out the key names\&. Regular expression matching is currently case\-sensitive and done against a canonicalized version of the key in which section and variable names are lowercased, but subsection names are not\&.
.RE
.PP
\-\-get\-urlmatch name URL
.RS 4
When given a two\-part name section\&.key, the value for section\&.<url>\&.key whose <url> part matches the best to the given URL is returned (if no such key exists, the value for section\&.key is used as a fallback)\&. When given just the section as name, do so for all the keys in the section and list them\&.
.RE
.PP
\-\-global
.RS 4
For writing options: write to global
~/\&.gitconfig
file rather than the repository
\&.git/config, write to
$XDG_CONFIG_HOME/git/config
file if this file exists and the
~/\&.gitconfig
file doesn\(cqt\&.
.sp
For reading options: read only from global
~/\&.gitconfig
and from
$XDG_CONFIG_HOME/git/config
rather than from all available files\&.
.sp
See also
the section called \(lqFILES\(rq\&.
.RE
.PP
\-\-system
.RS 4
For writing options: write to system\-wide
$(prefix)/etc/gitconfig
rather than the repository
\&.git/config\&.
.sp
For reading options: read only from system\-wide
$(prefix)/etc/gitconfig
rather than from all available files\&.
.sp
See also
the section called \(lqFILES\(rq\&.
.RE
.PP
\-\-local
.RS 4
For writing options: write to the repository
\&.git/config
file\&. This is the default behavior\&.
.sp
For reading options: read only from the repository
\&.git/config
rather than from all available files\&.
.sp
See also
the section called \(lqFILES\(rq\&.
.RE
.PP
\-f config\-file, \-\-file config\-file
.RS 4
Use the given config file instead of the one specified by GIT_CONFIG\&.
.RE
.PP
\-\-blob blob
.RS 4
Similar to
\fI\-\-file\fR
but use the given blob instead of a file\&. E\&.g\&. you can use
\fImaster:\&.gitmodules\fR
to read values from the file
\fI\&.gitmodules\fR
in the master branch\&. See "SPECIFYING REVISIONS" section in
\fBgitrevisions\fR(7)
for a more complete list of ways to spell blob names\&.
.RE
.PP
\-\-remove\-section
.RS 4
Remove the given section from the configuration file\&.
.RE
.PP
\-\-rename\-section
.RS 4
Rename the given section to a new name\&.
.RE
.PP
\-\-unset
.RS 4
Remove the line matching the key from config file\&.
.RE
.PP
\-\-unset\-all
.RS 4
Remove all lines matching the key from config file\&.
.RE
.PP
\-l, \-\-list
.RS 4
List all variables set in config file\&.
.RE
.PP
\-\-bool
.RS 4
\fIgit config\fR
will ensure that the output is "true" or "false"
.RE
.PP
\-\-int
.RS 4
\fIgit config\fR
will ensure that the output is a simple decimal number\&. An optional value suffix of
\fIk\fR,
\fIm\fR, or
\fIg\fR
in the config file will cause the value to be multiplied by 1024, 1048576, or 1073741824 prior to output\&.
.RE
.PP
\-\-bool\-or\-int
.RS 4
\fIgit config\fR
will ensure that the output matches the format of either \-\-bool or \-\-int, as described above\&.
.RE
.PP
\-\-path
.RS 4
\fIgit\-config\fR
will expand leading
\fI~\fR
to the value of
\fI$HOME\fR, and
\fI~user\fR
to the home directory for the specified user\&. This option has no effect when setting the value (but you can use
\fIgit config bla ~/\fR
from the command line to let your shell do the expansion)\&.
.RE
.PP
\-z, \-\-null
.RS 4
For all options that output values and/or keys, always end values with the null character (instead of a newline)\&. Use newline instead as a delimiter between key and value\&. This allows for secure parsing of the output without getting confused e\&.g\&. by values that contain line breaks\&.
.RE
.PP
\-\-get\-colorbool name [stdout\-is\-tty]
.RS 4
Find the color setting for
name
(e\&.g\&.
color\&.diff) and output "true" or "false"\&.
stdout\-is\-tty
should be either "true" or "false", and is taken into account when configuration says "auto"\&. If
stdout\-is\-tty
is missing, then checks the standard output of the command itself, and exits with status 0 if color is to be used, or exits with status 1 otherwise\&. When the color setting for
name
is undefined, the command uses
color\&.ui
as fallback\&.
.RE
.PP
\-\-get\-color name [default]
.RS 4
Find the color configured for
name
(e\&.g\&.
color\&.diff\&.new) and output it as the ANSI color escape sequence to the standard output\&. The optional
default
parameter is used instead, if there is no color configured for
name\&.
.RE
.PP
\-e, \-\-edit
.RS 4
Opens an editor to modify the specified config file; either
\fI\-\-system\fR,
\fI\-\-global\fR, or repository (default)\&.
.RE
.PP
\-\-[no\-]includes
.RS 4
Respect
include\&.*
directives in config files when looking up values\&. Defaults to on\&.
.RE
.SH "FILES"
.sp
If not set explicitly with \fI\-\-file\fR, there are four files where \fIgit config\fR will search for configuration options:
.PP
$(prefix)/etc/gitconfig
.RS 4
System\-wide configuration file\&.
.RE
.PP
$XDG_CONFIG_HOME/git/config
.RS 4
Second user\-specific configuration file\&. If $XDG_CONFIG_HOME is not set or empty,
$HOME/\&.config/git/config
will be used\&. Any single\-valued variable set in this file will be overwritten by whatever is in
~/\&.gitconfig\&. It is a good idea not to create this file if you sometimes use older versions of Git, as support for this file was added fairly recently\&.
.RE
.PP
~/\&.gitconfig
.RS 4
User\-specific configuration file\&. Also called "global" configuration file\&.
.RE
.PP
$GIT_DIR/config
.RS 4
Repository specific configuration file\&.
.RE
.sp
If no further options are given, all reading options will read all of these files that are available\&. If the global or the system\-wide configuration file are not available they will be ignored\&. If the repository configuration file is not available or readable, \fIgit config\fR will exit with a non\-zero error code\&. However, in neither case will an error message be issued\&.
.sp
The files are read in the order given above, with last value found taking precedence over values read earlier\&. When multiple values are taken then all values of a key from all files will be used\&.
.sp
All writing options will per default write to the repository specific configuration file\&. Note that this also affects options like \fI\-\-replace\-all\fR and \fI\-\-unset\fR\&. \fB\fIgit config\fR\fR\fB will only ever change one file at a time\fR\&.
.sp
You can override these rules either by command\-line options or by environment variables\&. The \fI\-\-global\fR and the \fI\-\-system\fR options will limit the file used to the global or system\-wide file respectively\&. The GIT_CONFIG environment variable has a similar effect, but you can specify any filename you want\&.
.SH "ENVIRONMENT"
.PP
GIT_CONFIG
.RS 4
Take the configuration from the given file instead of \&.git/config\&. Using the "\-\-global" option forces this to ~/\&.gitconfig\&. Using the "\-\-system" option forces this to $(prefix)/etc/gitconfig\&.
.RE
.PP
GIT_CONFIG_NOSYSTEM
.RS 4
Whether to skip reading settings from the system\-wide $(prefix)/etc/gitconfig file\&. See
\fBgit\fR(1)
for details\&.
.RE
.sp
See also the section called \(lqFILES\(rq\&.
.SH "EXAMPLES"
.sp
Given a \&.git/config like this:
.sp
.if n \{\
.RS 4
.\}
.nf
#
# This is the config file, and
# a \(aq#\(aq or \(aq;\(aq character indicates
# a comment
#
.fi
.if n \{\
.RE
.\}
.sp
.if n \{\
.RS 4
.\}
.nf
; core variables
[core]
        ; Don\(aqt trust file modes
        filemode = false
.fi
.if n \{\
.RE
.\}
.sp
.if n \{\
.RS 4
.\}
.nf
; Our diff algorithm
[diff]
        external = /usr/local/bin/diff\-wrapper
        renames = true
.fi
.if n \{\
.RE
.\}
.sp
.if n \{\
.RS 4
.\}
.nf
; Proxy settings
[core]
        gitproxy=proxy\-command for kernel\&.org
        gitproxy=default\-proxy ; for all the rest
.fi
.if n \{\
.RE
.\}
.sp
.if n \{\
.RS 4
.\}
.nf
; HTTP
[http]
        sslVerify
[http "https://weak\&.example\&.com"]
        sslVerify = false
        cookieFile = /tmp/cookie\&.txt
.fi
.if n \{\
.RE
.\}
.sp
you can set the filemode to true with
.sp
.if n \{\
.RS 4
.\}
.nf
% git config core\&.filemode true
.fi
.if n \{\
.RE
.\}
.sp
.sp
The hypothetical proxy command entries actually have a postfix to discern what URL they apply to\&. Here is how to change the entry for kernel\&.org to "ssh"\&.
.sp
.if n \{\
.RS 4
.\}
.nf
% git config core\&.gitproxy \(aq"ssh" for kernel\&.org\(aq \(aqfor kernel\&.org$\(aq
.fi
.if n \{\
.RE
.\}
.sp
.sp
This makes sure that only the key/value pair for kernel\&.org is replaced\&.
.sp
To delete the entry for renames, do
.sp
.if n \{\
.RS 4
.\}
.nf
% git config \-\-unset diff\&.renames
.fi
.if n \{\
.RE
.\}
.sp
.sp
If you want to delete an entry for a multivar (like core\&.gitproxy above), you have to provide a regex matching the value of exactly one line\&.
.sp
To query the value for a given key, do
.sp
.if n \{\
.RS 4
.\}
.nf
% git config \-\-get core\&.filemode
.fi
.if n \{\
.RE
.\}
.sp
.sp
or
.sp
.if n \{\
.RS 4
.\}
.nf
% git config core\&.filemode
.fi
.if n \{\
.RE
.\}
.sp
.sp
or, to query a multivar:
.sp
.if n \{\
.RS 4
.\}
.nf
% git config \-\-get core\&.gitproxy "for kernel\&.org$"
.fi
.if n \{\
.RE
.\}
.sp
.sp
If you want to know all the values for a multivar, do:
.sp
.if n \{\
.RS 4
.\}
.nf
% git config \-\-get\-all core\&.gitproxy
.fi
.if n \{\
.RE
.\}
.sp
.sp
If you like to live dangerously, you can replace \fBall\fR core\&.gitproxy by a new one with
.sp
.if n \{\
.RS 4
.\}
.nf
% git config \-\-replace\-all core\&.gitproxy ssh
.fi
.if n \{\
.RE
.\}
.sp
.sp
However, if you really only want to replace the line for the default proxy, i\&.e\&. the one without a "for \&..." postfix, do something like this:
.sp
.if n \{\
.RS 4
.\}
.nf
% git config core\&.gitproxy ssh \(aq! for \(aq
.fi
.if n \{\
.RE
.\}
.sp
.sp
To actually match only values with an exclamation mark, you have to
.sp
.if n \{\
.RS 4
.\}
.nf
% git config section\&.key value \(aq[!]\(aq
.fi
.if n \{\
.RE
.\}
.sp
.sp
To add a new proxy, without altering any of the existing ones, use
.sp
.if n \{\
.RS 4
.\}
.nf
% git config \-\-add core\&.gitproxy \(aq"proxy\-command" for example\&.com\(aq
.fi
.if n \{\
.RE
.\}
.sp
.sp
An example to use customized color from the configuration in your script:
.sp
.if n \{\
.RS 4
.\}
.nf
#!/bin/sh
WS=$(git config \-\-get\-color color\&.diff\&.whitespace "blue reverse")
RESET=$(git config \-\-get\-color "" "reset")
echo "${WS}your whitespace color or blue reverse${RESET}"
.fi
.if n \{\
.RE
.\}
.sp
.sp
For URLs in https://weak\&.example\&.com, http\&.sslVerify is set to false, while it is set to true for all others:
.sp
.if n \{\
.RS 4
.\}
.nf
% git config \-\-bool \-\-get\-urlmatch http\&.sslverify https://good\&.example\&.com
true
% git config \-\-bool \-\-get\-urlmatch http\&.sslverify https://weak\&.example\&.com
false
% git config \-\-get\-urlmatch http https://weak\&.example\&.com
http\&.cookieFile /tmp/cookie\&.txt
http\&.sslverify false
.fi
.if n \{\
.RE
.\}
.sp
.SH "CONFIGURATION FILE"
.sp
The Git configuration file contains a number of variables that affect the Git commands\(aq behavior\&. The \&.git/config file in each repository is used to store the configuration for that repository, and $HOME/\&.gitconfig is used to store a per\-user configuration as fallback values for the \&.git/config file\&. The file /etc/gitconfig can be used to store a system\-wide default configuration\&.
.sp
The configuration variables are used by both the Git plumbing and the porcelains\&. The variables are divided into sections, wherein the fully qualified variable name of the variable itself is the last dot\-separated segment and the section name is everything before the last dot\&. The variable names are case\-insensitive, allow only alphanumeric characters and \-, and must start with an alphabetic character\&. Some variables may appear multiple times; we say then that the variable is multivalued\&.
.SS "Syntax"
.sp
The syntax is fairly flexible and permissive; whitespaces are mostly ignored\&. The \fI#\fR and \fI;\fR characters begin comments to the end of line, blank lines are ignored\&.
.sp
The file consists of sections and variables\&. A section begins with the name of the section in square brackets and continues until the next section begins\&. Section names are case\-insensitive\&. Only alphanumeric characters, \- and \&. are allowed in section names\&. Each variable must belong to some section, which means that there must be a section header before the first setting of a variable\&.
.sp
Sections can be further divided into subsections\&. To begin a subsection put its name in double quotes, separated by space from the section name, in the section header, like in the example below:
.sp
.if n \{\
.RS 4
.\}
.nf
        [section "subsection"]
.fi
.if n \{\
.RE
.\}
.sp
.sp
Subsection names are case sensitive and can contain any characters except newline (doublequote " and backslash can be included by escaping them as \e" and \e\e, respectively)\&. Section headers cannot span multiple lines\&. Variables may belong directly to a section or to a given subsection\&. You can have [section] if you have [section "subsection"], but you don\(cqt need to\&.
.sp
There is also a deprecated [section\&.subsection] syntax\&. With this syntax, the subsection name is converted to lower\-case and is also compared case sensitively\&. These subsection names follow the same restrictions as section names\&.
.sp
All the other lines (and the remainder of the line after the section header) are recognized as setting variables, in the form \fIname = value\fR (or just \fIname\fR, which is a short\-hand to say that the variable is the boolean "true")\&. The variable names are case\-insensitive, allow only alphanumeric characters and \-, and must start with an alphabetic character\&.
.sp
A line that defines a value can be continued to the next line by ending it with a \e; the backquote and the end\-of\-line are stripped\&. Leading whitespaces after \fIname =\fR, the remainder of the line after the first comment character \fI#\fR or \fI;\fR, and trailing whitespaces of the line are discarded unless they are enclosed in double quotes\&. Internal whitespaces within the value are retained verbatim\&.
.sp
Inside double quotes, double quote " and backslash \e characters must be escaped: use \e" for " and \e\e for \e\&.
.sp
The following escape sequences (beside \e" and \e\e) are recognized: \en for newline character (NL), \et for horizontal tabulation (HT, TAB) and \eb for backspace (BS)\&. Other char escape sequences (including octal escape sequences) are invalid\&.
.SS "Includes"
.sp
You can include one config file from another by setting the special include\&.path variable to the name of the file to be included\&. The included file is expanded immediately, as if its contents had been found at the location of the include directive\&. If the value of the include\&.path variable is a relative path, the path is considered to be relative to the configuration file in which the include directive was found\&. The value of include\&.path is subject to tilde expansion: ~/ is expanded to the value of $HOME, and ~user/ to the specified user\(cqs home directory\&. See below for examples\&.
.SS "Example"
.sp
.if n \{\
.RS 4
.\}
.nf
# Core variables
[core]
        ; Don\(aqt trust file modes
        filemode = false
.fi
.if n \{\
.RE
.\}
.sp
.if n \{\
.RS 4
.\}
.nf
# Our diff algorithm
[diff]
        external = /usr/local/bin/diff\-wrapper
        renames = true
.fi
.if n \{\
.RE
.\}
.sp
.if n \{\
.RS 4
.\}
.nf
[branch "devel"]
        remote = origin
        merge = refs/heads/devel
.fi
.if n \{\
.RE
.\}
.sp
.if n \{\
.RS 4
.\}
.nf
# Proxy settings
[core]
        gitProxy="ssh" for "kernel\&.org"
        gitProxy=default\-proxy ; for the rest
.fi
.if n \{\
.RE
.\}
.sp
.if n \{\
.RS 4
.\}
.nf
[include]
        path = /path/to/foo\&.inc ; include by absolute path
        path = foo ; expand "foo" relative to the current file
        path = ~/foo ; expand "foo" in your $HOME directory
.fi
.if n \{\
.RE
.\}
.SS "Values"
.sp
Values of many variables are treated as a simple string, but there are variables that take values of specific types and there are rules as to how to spell them\&.
.PP
boolean
.RS 4
When a variable is said to take a boolean value, many synonyms are accepted for
\fItrue\fR
and
\fIfalse\fR; these are all case\-insensitive\&.
.PP
true
.RS 4
Boolean true can be spelled as
yes,
on,
true, or
1\&. Also, a variable defined without
= <value>
is taken as true\&.
.RE
.PP
false
.RS 4
Boolean false can be spelled as
no,
off,
false, or
0\&.
.sp
When converting value to the canonical form using
\fI\-\-bool\fR
type specifier;
\fIgit config\fR
will ensure that the output is "true" or "false" (spelled in lowercase)\&.
.RE
.RE
.PP
integer
.RS 4
The value for many variables that specify various sizes can be suffixed with
k,
M,\&... to mean "scale the number by 1024", "by 1024x1024", etc\&.
.RE
.PP
color
.RS 4
The value for a variables that takes a color is a list of colors (at most two) and attributes (at most one), separated by spaces\&. The colors accepted are
normal,
black,
red,
green,
yellow,
blue,
magenta,
cyan
and
white; the attributes are
bold,
dim,
ul,
blink
and
reverse\&. The first color given is the foreground; the second is the background\&. The position of the attribute, if any, doesn\(cqt matter\&. Attributes may be turned off specifically by prefixing them with
no
(e\&.g\&.,
noreverse,
noul, etc)\&.
.sp
Colors (foreground and background) may also be given as numbers between 0 and 255; these use ANSI 256\-color mode (but note that not all terminals may support this)\&. If your terminal supports it, you may also specify 24\-bit RGB values as hex, like
#ff0ab3\&.
.sp
The attributes are meant to be reset at the beginning of each item in the colored output, so setting color\&.decorate\&.branch to
black
will paint that branch name in a plain
black, even if the previous thing on the same output line (e\&.g\&. opening parenthesis before the list of branch names in
log \-\-decorate
output) is set to be painted with
bold
or some other attribute\&.
.RE
.SS "Variables"
.sp
Note that this list is non\-comprehensive and not necessarily complete\&. For command\-specific variables, you will find a more detailed description in the appropriate manual page\&.
.sp
Other git\-related tools may and do use their own variables\&. When inventing new variables for use in your own tool, make sure their names do not conflict with those that are used by Git itself and other popular tools, and describe them in your documentation\&.
.PP
advice\&.*
.RS 4
These variables control various optional help messages designed to aid new users\&. All
\fIadvice\&.*\fR
variables default to
\fItrue\fR, and you can tell Git that you do not need help by setting these to
\fIfalse\fR:
.PP
pushUpdateRejected
.RS 4
Set this variable to
\fIfalse\fR
if you want to disable
\fIpushNonFFCurrent\fR,
\fIpushNonFFMatching\fR,
\fIpushAlreadyExists\fR,
\fIpushFetchFirst\fR, and
\fIpushNeedsForce\fR
simultaneously\&.
.RE
.PP
pushNonFFCurrent
.RS 4
Advice shown when
\fBgit-push\fR(1)
fails due to a non\-fast\-forward update to the current branch\&.
.RE
.PP
pushNonFFMatching
.RS 4
Advice shown when you ran
\fBgit-push\fR(1)
and pushed
\fImatching refs\fR
explicitly (i\&.e\&. you used
\fI:\fR, or specified a refspec that isn\(cqt your current branch) and it resulted in a non\-fast\-forward error\&.
.RE
.PP
pushAlreadyExists
.RS 4
Shown when
\fBgit-push\fR(1)
rejects an update that does not qualify for fast\-forwarding (e\&.g\&., a tag\&.)
.RE
.PP
pushFetchFirst
.RS 4
Shown when
\fBgit-push\fR(1)
rejects an update that tries to overwrite a remote ref that points at an object we do not have\&.
.RE
.PP
pushNeedsForce
.RS 4
Shown when
\fBgit-push\fR(1)
rejects an update that tries to overwrite a remote ref that points at an object that is not a commit\-ish, or make the remote ref point at an object that is not a commit\-ish\&.
.RE
.PP
statusHints
.RS 4
Show directions on how to proceed from the current state in the output of
\fBgit-status\fR(1), in the template shown when writing commit messages in
\fBgit-commit\fR(1), and in the help message shown by
\fBgit-checkout\fR(1)
when switching branch\&.
.RE
.PP
statusUoption
.RS 4
Advise to consider using the
\-u
option to
\fBgit-status\fR(1)
when the command takes more than 2 seconds to enumerate untracked files\&.
.RE
.PP
commitBeforeMerge
.RS 4
Advice shown when
\fBgit-merge\fR(1)
refuses to merge to avoid overwriting local changes\&.
.RE
.PP
resolveConflict
.RS 4
Advice shown by various commands when conflicts prevent the operation from being performed\&.
.RE
.PP
implicitIdentity
.RS 4
Advice on how to set your identity configuration when your information is guessed from the system username and domain name\&.
.RE
.PP
detachedHead
.RS 4
Advice shown when you used
\fBgit-checkout\fR(1)
to move to the detach HEAD state, to instruct how to create a local branch after the fact\&.
.RE
.PP
amWorkDir
.RS 4
Advice that shows the location of the patch file when
\fBgit-am\fR(1)
fails to apply it\&.
.RE
.PP
rmHints
.RS 4
In case of failure in the output of
\fBgit-rm\fR(1), show directions on how to proceed from the current state\&.
.RE
.RE
.PP
core\&.fileMode
.RS 4
Tells Git if the executable bit of files in the working tree is to be honored\&.
.sp
Some filesystems lose the executable bit when a file that is marked as executable is checked out, or checks out an non\-executable file with executable bit on\&.
\fBgit-clone\fR(1)
or
\fBgit-init\fR(1)
probe the filesystem to see if it handles the executable bit correctly and this variable is automatically set as necessary\&.
.sp
A repository, however, may be on a filesystem that handles the filemode correctly, and this variable is set to
\fItrue\fR
when created, but later may be made accessible from another environment that loses the filemode (e\&.g\&. exporting ext4 via CIFS mount, visiting a Cygwin created repository with Git for Windows or Eclipse)\&. In such a case it may be necessary to set this variable to
\fIfalse\fR\&. See
\fBgit-update-index\fR(1)\&.
.sp
The default is true (when core\&.filemode is not specified in the config file)\&.
.RE
.PP
core\&.ignoreCase
.RS 4
If true, this option enables various workarounds to enable Git to work better on filesystems that are not case sensitive, like FAT\&. For example, if a directory listing finds "makefile" when Git expects "Makefile", Git will assume it is really the same file, and continue to remember it as "Makefile"\&.
.sp
The default is false, except
\fBgit-clone\fR(1)
or
\fBgit-init\fR(1)
will probe and set core\&.ignoreCase true if appropriate when the repository is created\&.
.RE
.PP
core\&.precomposeUnicode
.RS 4
This option is only used by Mac OS implementation of Git\&. When core\&.precomposeUnicode=true, Git reverts the unicode decomposition of filenames done by Mac OS\&. This is useful when sharing a repository between Mac OS and Linux or Windows\&. (Git for Windows 1\&.7\&.10 or higher is needed, or Git under cygwin 1\&.7)\&. When false, file names are handled fully transparent by Git, which is backward compatible with older versions of Git\&.
.RE
.PP
core\&.protectHFS
.RS 4
If set to true, do not allow checkout of paths that would be considered equivalent to
\&.git
on an HFS+ filesystem\&. Defaults to
true
on Mac OS, and
false
elsewhere\&.
.RE
.PP
core\&.protectNTFS
.RS 4
If set to true, do not allow checkout of paths that would cause problems with the NTFS filesystem, e\&.g\&. conflict with 8\&.3 "short" names\&. Defaults to
true
on Windows, and
false
elsewhere\&.
.RE
.PP
core\&.trustctime
.RS 4
If false, the ctime differences between the index and the working tree are ignored; useful when the inode change time is regularly modified by something outside Git (file system crawlers and some backup systems)\&. See
\fBgit-update-index\fR(1)\&. True by default\&.
.RE
.PP
core\&.checkStat
.RS 4
Determines which stat fields to match between the index and work tree\&. The user can set this to
\fIdefault\fR
or
\fIminimal\fR\&. Default (or explicitly
\fIdefault\fR), is to check all fields, including the sub\-second part of mtime and ctime\&.
.RE
.PP
core\&.quotePath
.RS 4
The commands that output paths (e\&.g\&.
\fIls\-files\fR,
\fIdiff\fR), when not given the
\-z
option, will quote "unusual" characters in the pathname by enclosing the pathname in a double\-quote pair and with backslashes the same way strings in C source code are quoted\&. If this variable is set to false, the bytes higher than 0x80 are not quoted but output as verbatim\&. Note that double quote, backslash and control characters are always quoted without
\-z
regardless of the setting of this variable\&.
.RE
.PP
core\&.eol
.RS 4
Sets the line ending type to use in the working directory for files that have the
text
property set\&. Alternatives are
\fIlf\fR,
\fIcrlf\fR
and
\fInative\fR, which uses the platform\(cqs native line ending\&. The default value is
native\&. See
\fBgitattributes\fR(5)
for more information on end\-of\-line conversion\&.
.RE
.PP
core\&.safecrlf
.RS 4
If true, makes Git check if converting
CRLF
is reversible when end\-of\-line conversion is active\&. Git will verify if a command modifies a file in the work tree either directly or indirectly\&. For example, committing a file followed by checking out the same file should yield the original file in the work tree\&. If this is not the case for the current setting of
core\&.autocrlf, Git will reject the file\&. The variable can be set to "warn", in which case Git will only warn about an irreversible conversion but continue the operation\&.
.sp
CRLF conversion bears a slight chance of corrupting data\&. When it is enabled, Git will convert CRLF to LF during commit and LF to CRLF during checkout\&. A file that contains a mixture of LF and CRLF before the commit cannot be recreated by Git\&. For text files this is the right thing to do: it corrects line endings such that we have only LF line endings in the repository\&. But for binary files that are accidentally classified as text the conversion can corrupt data\&.
.sp
If you recognize such corruption early you can easily fix it by setting the conversion type explicitly in \&.gitattributes\&. Right after committing you still have the original file in your work tree and this file is not yet corrupted\&. You can explicitly tell Git that this file is binary and Git will handle the file appropriately\&.
.sp
Unfortunately, the desired effect of cleaning up text files with mixed line endings and the undesired effect of corrupting binary files cannot be distinguished\&. In both cases CRLFs are removed in an irreversible way\&. For text files this is the right thing to do because CRLFs are line endings, while for binary files converting CRLFs corrupts data\&.
.sp
Note, this safety check does not mean that a checkout will generate a file identical to the original file for a different setting of
core\&.eol
and
core\&.autocrlf, but only for the current one\&. For example, a text file with
LF
would be accepted with
core\&.eol=lf
and could later be checked out with
core\&.eol=crlf, in which case the resulting file would contain
CRLF, although the original file contained
LF\&. However, in both work trees the line endings would be consistent, that is either all
LF
or all
CRLF, but never mixed\&. A file with mixed line endings would be reported by the
core\&.safecrlf
mechanism\&.
.RE
.PP
core\&.autocrlf
.RS 4
Setting this variable to "true" is almost the same as setting the
text
attribute to "auto" on all files except that text files are not guaranteed to be normalized: files that contain
CRLF
in the repository will not be touched\&. Use this setting if you want to have
CRLF
line endings in your working directory even though the repository does not have normalized line endings\&. This variable can be set to
\fIinput\fR, in which case no output conversion is performed\&.
.RE
.PP
core\&.symlinks
.RS 4
If false, symbolic links are checked out as small plain files that contain the link text\&.
\fBgit-update-index\fR(1)
and
\fBgit-add\fR(1)
will not change the recorded type to regular file\&. Useful on filesystems like FAT that do not support symbolic links\&.
.sp
The default is true, except
\fBgit-clone\fR(1)
or
\fBgit-init\fR(1)
will probe and set core\&.symlinks false if appropriate when the repository is created\&.
.RE
.PP
core\&.gitProxy
.RS 4
A "proxy command" to execute (as
\fIcommand host port\fR) instead of establishing direct connection to the remote server when using the Git protocol for fetching\&. If the variable value is in the "COMMAND for DOMAIN" format, the command is applied only on hostnames ending with the specified domain string\&. This variable may be set multiple times and is matched in the given order; the first match wins\&.
.sp
Can be overridden by the
\fIGIT_PROXY_COMMAND\fR
environment variable (which always applies universally, without the special "for" handling)\&.
.sp
The special string
none
can be used as the proxy command to specify that no proxy be used for a given domain pattern\&. This is useful for excluding servers inside a firewall from proxy use, while defaulting to a common proxy for external domains\&.
.RE
.PP
core\&.ignoreStat
.RS 4
If true, Git will avoid using lstat() calls to detect if files have changed by setting the "assume\-unchanged" bit for those tracked files which it has updated identically in both the index and working tree\&.
.sp
When files are modified outside of Git, the user will need to stage the modified files explicitly (e\&.g\&. see
\fIExamples\fR
section in
\fBgit-update-index\fR(1))\&. Git will not normally detect changes to those files\&.
.sp
This is useful on systems where lstat() calls are very slow, such as CIFS/Microsoft Windows\&.
.sp
False by default\&.
.RE
.PP
core\&.preferSymlinkRefs
.RS 4
Instead of the default "symref" format for HEAD and other symbolic reference files, use symbolic links\&. This is sometimes needed to work with old scripts that expect HEAD to be a symbolic link\&.
.RE
.PP
core\&.bare
.RS 4
If true this repository is assumed to be
\fIbare\fR
and has no working directory associated with it\&. If this is the case a number of commands that require a working directory will be disabled, such as
\fBgit-add\fR(1)
or
\fBgit-merge\fR(1)\&.
.sp
This setting is automatically guessed by
\fBgit-clone\fR(1)
or
\fBgit-init\fR(1)
when the repository was created\&. By default a repository that ends in "/\&.git" is assumed to be not bare (bare = false), while all other repositories are assumed to be bare (bare = true)\&.
.RE
.PP
core\&.worktree
.RS 4
Set the path to the root of the working tree\&. If GIT_COMMON_DIR environment variable is set, core\&.worktree is ignored and not used for determining the root of working tree\&. This can be overridden by the GIT_WORK_TREE environment variable and the
\fI\-\-work\-tree\fR
command\-line option\&. The value can be an absolute path or relative to the path to the \&.git directory, which is either specified by \-\-git\-dir or GIT_DIR, or automatically discovered\&. If \-\-git\-dir or GIT_DIR is specified but none of \-\-work\-tree, GIT_WORK_TREE and core\&.worktree is specified, the current working directory is regarded as the top level of your working tree\&.
.sp
Note that this variable is honored even when set in a configuration file in a "\&.git" subdirectory of a directory and its value differs from the latter directory (e\&.g\&. "/path/to/\&.git/config" has core\&.worktree set to "/different/path"), which is most likely a misconfiguration\&. Running Git commands in the "/path/to" directory will still use "/different/path" as the root of the work tree and can cause confusion unless you know what you are doing (e\&.g\&. you are creating a read\-only snapshot of the same index to a location different from the repository\(cqs usual working tree)\&.
.RE
.PP
core\&.logAllRefUpdates
.RS 4
Enable the reflog\&. Updates to a ref <ref> is logged to the file "$GIT_DIR/logs/<ref>", by appending the new and old SHA\-1, the date/time and the reason of the update, but only when the file exists\&. If this configuration variable is set to true, missing "$GIT_DIR/logs/<ref>" file is automatically created for branch heads (i\&.e\&. under refs/heads/), remote refs (i\&.e\&. under refs/remotes/), note refs (i\&.e\&. under refs/notes/), and the symbolic ref HEAD\&.
.sp
This information can be used to determine what commit was the tip of a branch "2 days ago"\&.
.sp
This value is true by default in a repository that has a working directory associated with it, and false by default in a bare repository\&.
.RE
.PP
core\&.repositoryFormatVersion
.RS 4
Internal variable identifying the repository format and layout version\&.
.RE
.PP
core\&.sharedRepository
.RS 4
When
\fIgroup\fR
(or
\fItrue\fR), the repository is made shareable between several users in a group (making sure all the files and objects are group\-writable)\&. When
\fIall\fR
(or
\fIworld\fR
or
\fIeverybody\fR), the repository will be readable by all users, additionally to being group\-shareable\&. When
\fIumask\fR
(or
\fIfalse\fR), Git will use permissions reported by umask(2)\&. When
\fI0xxx\fR, where
\fI0xxx\fR
is an octal number, files in the repository will have this mode value\&.
\fI0xxx\fR
will override user\(cqs umask value (whereas the other options will only override requested parts of the user\(cqs umask value)\&. Examples:
\fI0660\fR
will make the repo read/write\-able for the owner and group, but inaccessible to others (equivalent to
\fIgroup\fR
unless umask is e\&.g\&.
\fI0022\fR)\&.
\fI0640\fR
is a repository that is group\-readable but not group\-writable\&. See
\fBgit-init\fR(1)\&. False by default\&.
.RE
.PP
core\&.warnAmbiguousRefs
.RS 4
If true, Git will warn you if the ref name you passed it is ambiguous and might match multiple refs in the repository\&. True by default\&.
.RE
.PP
core\&.compression
.RS 4
An integer \-1\&.\&.9, indicating a default compression level\&. \-1 is the zlib default\&. 0 means no compression, and 1\&.\&.9 are various speed/size tradeoffs, 9 being slowest\&. If set, this provides a default to other compression variables, such as
\fIcore\&.looseCompression\fR
and
\fIpack\&.compression\fR\&.
.RE
.PP
core\&.looseCompression
.RS 4
An integer \-1\&.\&.9, indicating the compression level for objects that are not in a pack file\&. \-1 is the zlib default\&. 0 means no compression, and 1\&.\&.9 are various speed/size tradeoffs, 9 being slowest\&. If not set, defaults to core\&.compression\&. If that is not set, defaults to 1 (best speed)\&.
.RE
.PP
core\&.packedGitWindowSize
.RS 4
Number of bytes of a pack file to map into memory in a single mapping operation\&. Larger window sizes may allow your system to process a smaller number of large pack files more quickly\&. Smaller window sizes will negatively affect performance due to increased calls to the operating system\(cqs memory manager, but may improve performance when accessing a large number of large pack files\&.
.sp
Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32 MiB on 32 bit platforms and 1 GiB on 64 bit platforms\&. This should be reasonable for all users/operating systems\&. You probably do not need to adjust this value\&.
.sp
Common unit suffixes of
\fIk\fR,
\fIm\fR, or
\fIg\fR
are supported\&.
.RE
.PP
core\&.packedGitLimit
.RS 4
Maximum number of bytes to map simultaneously into memory from pack files\&. If Git needs to access more than this many bytes at once to complete an operation it will unmap existing regions to reclaim virtual address space within the process\&.
.sp
Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms\&. This should be reasonable for all users/operating systems, except on the largest projects\&. You probably do not need to adjust this value\&.
.sp
Common unit suffixes of
\fIk\fR,
\fIm\fR, or
\fIg\fR
are supported\&.
.RE
.PP
core\&.deltaBaseCacheLimit
.RS 4
Maximum number of bytes to reserve for caching base objects that may be referenced by multiple deltified objects\&. By storing the entire decompressed base objects in a cache Git is able to avoid unpacking and decompressing frequently used base objects multiple times\&.
.sp
Default is 96 MiB on all platforms\&. This should be reasonable for all users/operating systems, except on the largest projects\&. You probably do not need to adjust this value\&.
.sp
Common unit suffixes of
\fIk\fR,
\fIm\fR, or
\fIg\fR
are supported\&.
.RE
.PP
core\&.bigFileThreshold
.RS 4
Files larger than this size are stored deflated, without attempting delta compression\&. Storing large files without delta compression avoids excessive memory usage, at the slight expense of increased disk usage\&. Additionally files larger than this size are always treated as binary\&.
.sp
Default is 512 MiB on all platforms\&. This should be reasonable for most projects as source code and other text files can still be delta compressed, but larger binary media files won\(cqt be\&.
.sp
Common unit suffixes of
\fIk\fR,
\fIm\fR, or
\fIg\fR
are supported\&.
.RE
.PP
core\&.excludesFile
.RS 4
In addition to
\fI\&.gitignore\fR
(per\-directory) and
\fI\&.git/info/exclude\fR, Git looks into this file for patterns of files which are not meant to be tracked\&. "~/" is expanded to the value of
$HOME
and "~user/" to the specified user\(cqs home directory\&. Its default value is $XDG_CONFIG_HOME/git/ignore\&. If $XDG_CONFIG_HOME is either not set or empty, $HOME/\&.config/git/ignore is used instead\&. See
\fBgitignore\fR(5)\&.
.RE
.PP
core\&.askPass
.RS 4
Some commands (e\&.g\&. svn and http interfaces) that interactively ask for a password can be told to use an external program given via the value of this variable\&. Can be overridden by the
\fIGIT_ASKPASS\fR
environment variable\&. If not set, fall back to the value of the
\fISSH_ASKPASS\fR
environment variable or, failing that, a simple password prompt\&. The external program shall be given a suitable prompt as command\-line argument and write the password on its STDOUT\&.
.RE
.PP
core\&.attributesFile
.RS 4
In addition to
\fI\&.gitattributes\fR
(per\-directory) and
\fI\&.git/info/attributes\fR, Git looks into this file for attributes (see
\fBgitattributes\fR(5))\&. Path expansions are made the same way as for
core\&.excludesFile\&. Its default value is $XDG_CONFIG_HOME/git/attributes\&. If $XDG_CONFIG_HOME is either not set or empty, $HOME/\&.config/git/attributes is used instead\&.
.RE
.PP
core\&.editor
.RS 4
Commands such as
commit
and
tag
that lets you edit messages by launching an editor uses the value of this variable when it is set, and the environment variable
GIT_EDITOR
is not set\&. See
\fBgit-var\fR(1)\&.
.RE
.PP
core\&.commentChar
.RS 4
Commands such as
commit
and
tag
that lets you edit messages consider a line that begins with this character commented, and removes them after the editor returns (default
\fI#\fR)\&.
.sp
If set to "auto",
git\-commit
would select a character that is not the beginning character of any line in existing commit messages\&.
.RE
.PP
core\&.packedRefsTimeout
.RS 4
The length of time, in milliseconds, to retry when trying to lock the
packed\-refs
file\&. Value 0 means not to retry at all; \-1 means to try indefinitely\&. Default is 1000 (i\&.e\&., retry for 1 second)\&.
.RE
.PP
sequence\&.editor
.RS 4
Text editor used by
git rebase \-i
for editing the rebase instruction file\&. The value is meant to be interpreted by the shell when it is used\&. It can be overridden by the
GIT_SEQUENCE_EDITOR
environment variable\&. When not configured the default commit message editor is used instead\&.
.RE
.PP
core\&.pager
.RS 4
Text viewer for use by Git commands (e\&.g\&.,
\fIless\fR)\&. The value is meant to be interpreted by the shell\&. The order of preference is the
$GIT_PAGER
environment variable, then
core\&.pager
configuration, then
$PAGER, and then the default chosen at compile time (usually
\fIless\fR)\&.
.sp
When the
LESS
environment variable is unset, Git sets it to
FRX
(if
LESS
environment variable is set, Git does not change it at all)\&. If you want to selectively override Git\(cqs default setting for
LESS, you can set
core\&.pager
to e\&.g\&.
less \-S\&. This will be passed to the shell by Git, which will translate the final command to
LESS=FRX less \-S\&. The environment does not set the
S
option but the command line does, instructing less to truncate long lines\&. Similarly, setting
core\&.pager
to
less \-+F
will deactivate the
F
option specified by the environment from the command\-line, deactivating the "quit if one screen" behavior of
less\&. One can specifically activate some flags for particular commands: for example, setting
pager\&.blame
to
less \-S
enables line truncation only for
git blame\&.
.sp
Likewise, when the
LV
environment variable is unset, Git sets it to
\-c\&. You can override this setting by exporting
LV
with another value or setting
core\&.pager
to
lv +c\&.
.RE
.PP
core\&.whitespace
.RS 4
A comma separated list of common whitespace problems to notice\&.
\fIgit diff\fR
will use
color\&.diff\&.whitespace
to highlight them, and
\fIgit apply \-\-whitespace=error\fR
will consider them as errors\&. You can prefix
\-
to disable any of them (e\&.g\&.
\-trailing\-space):
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
blank\-at\-eol
treats trailing whitespaces at the end of the line as an error (enabled by default)\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
space\-before\-tab
treats a space character that appears immediately before a tab character in the initial indent part of the line as an error (enabled by default)\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
indent\-with\-non\-tab
treats a line that is indented with space characters instead of the equivalent tabs as an error (not enabled by default)\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
tab\-in\-indent
treats a tab character in the initial indent part of the line as an error (not enabled by default)\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
blank\-at\-eof
treats blank lines added at the end of file as an error (enabled by default)\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
trailing\-space
is a short\-hand to cover both
blank\-at\-eol
and
blank\-at\-eof\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
cr\-at\-eol
treats a carriage\-return at the end of line as part of the line terminator, i\&.e\&. with it,
trailing\-space
does not trigger if the character before such a carriage\-return is not a whitespace (not enabled by default)\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
tabwidth=<n>
tells how many character positions a tab occupies; this is relevant for
indent\-with\-non\-tab
and when Git fixes
tab\-in\-indent
errors\&. The default tab width is 8\&. Allowed values are 1 to 63\&.
.RE
.RE
.PP
core\&.fsyncObjectFiles
.RS 4
This boolean will enable
\fIfsync()\fR
when writing object files\&.
.sp
This is a total waste of time and effort on a filesystem that orders data writes properly, but can be useful for filesystems that do not use journalling (traditional UNIX filesystems) or that only journal metadata and not file contents (OS X\(cqs HFS+, or Linux ext3 with "data=writeback")\&.
.RE
.PP
core\&.preloadIndex
.RS 4
Enable parallel index preload for operations like
\fIgit diff\fR
.sp
This can speed up operations like
\fIgit diff\fR
and
\fIgit status\fR
especially on filesystems like NFS that have weak caching semantics and thus relatively high IO latencies\&. When enabled, Git will do the index comparison to the filesystem data in parallel, allowing overlapping IO\(cqs\&. Defaults to true\&.
.RE
.PP
core\&.createObject
.RS 4
You can set this to
\fIlink\fR, in which case a hardlink followed by a delete of the source are used to make sure that object creation will not overwrite existing objects\&.
.sp
On some file system/operating system combinations, this is unreliable\&. Set this config setting to
\fIrename\fR
there; However, This will remove the check that makes sure that existing object files will not get overwritten\&.
.RE
.PP
core\&.notesRef
.RS 4
When showing commit messages, also show notes which are stored in the given ref\&. The ref must be fully qualified\&. If the given ref does not exist, it is not an error but means that no notes should be printed\&.
.sp
This setting defaults to "refs/notes/commits", and it can be overridden by the
\fIGIT_NOTES_REF\fR
environment variable\&. See
\fBgit-notes\fR(1)\&.
.RE
.PP
core\&.sparseCheckout
.RS 4
Enable "sparse checkout" feature\&. See section "Sparse checkout" in
\fBgit-read-tree\fR(1)
for more information\&.
.RE
.PP
core\&.abbrev
.RS 4
Set the length object names are abbreviated to\&. If unspecified, many commands abbreviate to 7 hexdigits, which may not be enough for abbreviated object names to stay unique for sufficiently long time\&.
.RE
.PP
add\&.ignoreErrors, add\&.ignore\-errors (deprecated)
.RS 4
Tells
\fIgit add\fR
to continue adding files when some files cannot be added due to indexing errors\&. Equivalent to the
\fI\-\-ignore\-errors\fR
option of
\fBgit-add\fR(1)\&.
add\&.ignore\-errors
is deprecated, as it does not follow the usual naming convention for configuration variables\&.
.RE
.PP
alias\&.*
.RS 4
Command aliases for the
\fBgit\fR(1)
command wrapper \- e\&.g\&. after defining "alias\&.last = cat\-file commit HEAD", the invocation "git last" is equivalent to "git cat\-file commit HEAD"\&. To avoid confusion and troubles with script usage, aliases that hide existing Git commands are ignored\&. Arguments are split by spaces, the usual shell quoting and escaping is supported\&. A quote pair or a backslash can be used to quote them\&.
.sp
If the alias expansion is prefixed with an exclamation point, it will be treated as a shell command\&. For example, defining "alias\&.new = !gitk \-\-all \-\-not ORIG_HEAD", the invocation "git new" is equivalent to running the shell command "gitk \-\-all \-\-not ORIG_HEAD"\&. Note that shell commands will be executed from the top\-level directory of a repository, which may not necessarily be the current directory\&.
\fIGIT_PREFIX\fR
is set as returned by running
\fIgit rev\-parse \-\-show\-prefix\fR
from the original current directory\&. See
\fBgit-rev-parse\fR(1)\&.
.RE
.PP
am\&.keepcr
.RS 4
If true, git\-am will call git\-mailsplit for patches in mbox format with parameter
\fI\-\-keep\-cr\fR\&. In this case git\-mailsplit will not remove
\er
from lines ending with
\er\en\&. Can be overridden by giving
\fI\-\-no\-keep\-cr\fR
from the command line\&. See
\fBgit-am\fR(1),
\fBgit-mailsplit\fR(1)\&.
.RE
.PP
am\&.threeWay
.RS 4
By default,
git am
will fail if the patch does not apply cleanly\&. When set to true, this setting tells
git am
to fall back on 3\-way merge if the patch records the identity of blobs it is supposed to apply to and we have those blobs available locally (equivalent to giving the
\-\-3way
option from the command line)\&. Defaults to
false\&. See
\fBgit-am\fR(1)\&.
.RE
.PP
apply\&.ignoreWhitespace
.RS 4
When set to
\fIchange\fR, tells
\fIgit apply\fR
to ignore changes in whitespace, in the same way as the
\fI\-\-ignore\-space\-change\fR
option\&. When set to one of: no, none, never, false tells
\fIgit apply\fR
to respect all whitespace differences\&. See
\fBgit-apply\fR(1)\&.
.RE
.PP
apply\&.whitespace
.RS 4
Tells
\fIgit apply\fR
how to handle whitespaces, in the same way as the
\fI\-\-whitespace\fR
option\&. See
\fBgit-apply\fR(1)\&.
.RE
.PP
branch\&.autoSetupMerge
.RS 4
Tells
\fIgit branch\fR
and
\fIgit checkout\fR
to set up new branches so that
\fBgit-pull\fR(1)
will appropriately merge from the starting point branch\&. Note that even if this option is not set, this behavior can be chosen per\-branch using the
\-\-track
and
\-\-no\-track
options\&. The valid settings are:
false \(em no automatic setup is done;
true \(em automatic setup is done when the starting point is a remote\-tracking branch;
always \(em  automatic setup is done when the starting point is either a local branch or remote\-tracking branch\&. This option defaults to true\&.
.RE
.PP
branch\&.autoSetupRebase
.RS 4
When a new branch is created with
\fIgit branch\fR
or
\fIgit checkout\fR
that tracks another branch, this variable tells Git to set up pull to rebase instead of merge (see "branch\&.<name>\&.rebase")\&. When
never, rebase is never automatically set to true\&. When
local, rebase is set to true for tracked branches of other local branches\&. When
remote, rebase is set to true for tracked branches of remote\-tracking branches\&. When
always, rebase will be set to true for all tracking branches\&. See "branch\&.autoSetupMerge" for details on how to set up a branch to track another branch\&. This option defaults to never\&.
.RE
.PP
branch\&.<name>\&.remote
.RS 4
When on branch <name>, it tells
\fIgit fetch\fR
and
\fIgit push\fR
which remote to fetch from/push to\&. The remote to push to may be overridden with
remote\&.pushDefault
(for all branches)\&. The remote to push to, for the current branch, may be further overridden by
branch\&.<name>\&.pushRemote\&. If no remote is configured, or if you are not on any branch, it defaults to
origin
for fetching and
remote\&.pushDefault
for pushing\&. Additionally,
\&.
(a period) is the current local repository (a dot\-repository), see
branch\&.<name>\&.merge\(aqs final note below\&.
.RE
.PP
branch\&.<name>\&.pushRemote
.RS 4
When on branch <name>, it overrides
branch\&.<name>\&.remote
for pushing\&. It also overrides
remote\&.pushDefault
for pushing from branch <name>\&. When you pull from one place (e\&.g\&. your upstream) and push to another place (e\&.g\&. your own publishing repository), you would want to set
remote\&.pushDefault
to specify the remote to push to for all branches, and use this option to override it for a specific branch\&.
.RE
.PP
branch\&.<name>\&.merge
.RS 4
Defines, together with branch\&.<name>\&.remote, the upstream branch for the given branch\&. It tells
\fIgit fetch\fR/\fIgit pull\fR/\fIgit rebase\fR
which branch to merge and can also affect
\fIgit push\fR
(see push\&.default)\&. When in branch <name>, it tells
\fIgit fetch\fR
the default refspec to be marked for merging in FETCH_HEAD\&. The value is handled like the remote part of a refspec, and must match a ref which is fetched from the remote given by "branch\&.<name>\&.remote"\&. The merge information is used by
\fIgit pull\fR
(which at first calls
\fIgit fetch\fR) to lookup the default branch for merging\&. Without this option,
\fIgit pull\fR
defaults to merge the first refspec fetched\&. Specify multiple values to get an octopus merge\&. If you wish to setup
\fIgit pull\fR
so that it merges into <name> from another branch in the local repository, you can point branch\&.<name>\&.merge to the desired branch, and use the relative path setting
\&.
(a period) for branch\&.<name>\&.remote\&.
.RE
.PP
branch\&.<name>\&.mergeOptions
.RS 4
Sets default options for merging into branch <name>\&. The syntax and supported options are the same as those of
\fBgit-merge\fR(1), but option values containing whitespace characters are currently not supported\&.
.RE
.PP
branch\&.<name>\&.rebase
.RS 4
When true, rebase the branch <name> on top of the fetched branch, instead of merging the default branch from the default remote when "git pull" is run\&. See "pull\&.rebase" for doing this in a non branch\-specific manner\&.
.sp
.if n \{\
.RS 4
.\}
.nf
When preserve, also pass `\-\-preserve\-merges` along to \(aqgit rebase\(aq
so that locally committed merge commits will not be flattened
by running \(aqgit pull\(aq\&.
.fi
.if n \{\
.RE
.\}
.sp
\fBNOTE\fR: this is a possibly dangerous operation; do
\fBnot\fR
use it unless you understand the implications (see
\fBgit-rebase\fR(1)
for details)\&.
.RE
.PP
branch\&.<name>\&.description
.RS 4
Branch description, can be edited with
git branch \-\-edit\-description\&. Branch description is automatically added in the format\-patch cover letter or request\-pull summary\&.
.RE
.PP
browser\&.<tool>\&.cmd
.RS 4
Specify the command to invoke the specified browser\&. The specified command is evaluated in shell with the URLs passed as arguments\&. (See
\fBgit-web--browse\fR(1)\&.)
.RE
.PP
browser\&.<tool>\&.path
.RS 4
Override the path for the given tool that may be used to browse HTML help (see
\fI\-w\fR
option in
\fBgit-help\fR(1)) or a working repository in gitweb (see
\fBgit-instaweb\fR(1))\&.
.RE
.PP
clean\&.requireForce
.RS 4
A boolean to make git\-clean do nothing unless given \-f, \-i or \-n\&. Defaults to true\&.
.RE
.PP
color\&.branch
.RS 4
A boolean to enable/disable color in the output of
\fBgit-branch\fR(1)\&. May be set to
always,
false
(or
never) or
auto
(or
true), in which case colors are used only when the output is to a terminal\&. Defaults to false\&.
.RE
.PP
color\&.branch\&.<slot>
.RS 4
Use customized color for branch coloration\&.
<slot>
is one of
current
(the current branch),
local
(a local branch),
remote
(a remote\-tracking branch in refs/remotes/),
upstream
(upstream tracking branch),
plain
(other refs)\&.
.RE
.PP
color\&.diff
.RS 4
Whether to use ANSI escape sequences to add color to patches\&. If this is set to
always,
\fBgit-diff\fR(1),
\fBgit-log\fR(1), and
\fBgit-show\fR(1)
will use color for all patches\&. If it is set to
true
or
auto, those commands will only use color when output is to the terminal\&. Defaults to false\&.
.sp
This does not affect
\fBgit-format-patch\fR(1)
or the
\fIgit\-diff\-*\fR
plumbing commands\&. Can be overridden on the command line with the
\-\-color[=<when>]
option\&.
.RE
.PP
color\&.diff\&.<slot>
.RS 4
Use customized color for diff colorization\&.
<slot>
specifies which part of the patch to use the specified color, and is one of
context
(context text \-
plain
is a historical synonym),
meta
(metainformation),
frag
(hunk header),
\fIfunc\fR
(function in hunk header),
old
(removed lines),
new
(added lines),
commit
(commit headers), or
whitespace
(highlighting whitespace errors)\&.
.RE
.PP
color\&.decorate\&.<slot>
.RS 4
Use customized color for
\fIgit log \-\-decorate\fR
output\&.
<slot>
is one of
branch,
remoteBranch,
tag,
stash
or
HEAD
for local branches, remote\-tracking branches, tags, stash and HEAD, respectively\&.
.RE
.PP
color\&.grep
.RS 4
When set to
always, always highlight matches\&. When
false
(or
never), never\&. When set to
true
or
auto, use color only when the output is written to the terminal\&. Defaults to
false\&.
.RE
.PP
color\&.grep\&.<slot>
.RS 4
Use customized color for grep colorization\&.
<slot>
specifies which part of the line to use the specified color, and is one of
.PP
context
.RS 4
non\-matching text in context lines (when using
\-A,
\-B, or
\-C)
.RE
.PP
filename
.RS 4
filename prefix (when not using
\-h)
.RE
.PP
function
.RS 4
function name lines (when using
\-p)
.RE
.PP
linenumber
.RS 4
line number prefix (when using
\-n)
.RE
.PP
match
.RS 4
matching text (same as setting
matchContext
and
matchSelected)
.RE
.PP
matchContext
.RS 4
matching text in context lines
.RE
.PP
matchSelected
.RS 4
matching text in selected lines
.RE
.PP
selected
.RS 4
non\-matching text in selected lines
.RE
.PP
separator
.RS 4
separators between fields on a line (:,
\-, and
=) and between hunks (\-\-)
.RE
.RE
.PP
color\&.interactive
.RS 4
When set to
always, always use colors for interactive prompts and displays (such as those used by "git\-add \-\-interactive" and "git\-clean \-\-interactive")\&. When false (or
never), never\&. When set to
true
or
auto, use colors only when the output is to the terminal\&. Defaults to false\&.
.RE
.PP
color\&.interactive\&.<slot>
.RS 4
Use customized color for
\fIgit add \-\-interactive\fR
and
\fIgit clean \-\-interactive\fR
output\&.
<slot>
may be
prompt,
header,
help
or
error, for four distinct types of normal output from interactive commands\&.
.RE
.PP
color\&.pager
.RS 4
A boolean to enable/disable colored output when the pager is in use (default is true)\&.
.RE
.PP
color\&.showBranch
.RS 4
A boolean to enable/disable color in the output of
\fBgit-show-branch\fR(1)\&. May be set to
always,
false
(or
never) or
auto
(or
true), in which case colors are used only when the output is to a terminal\&. Defaults to false\&.
.RE
.PP
color\&.status
.RS 4
A boolean to enable/disable color in the output of
\fBgit-status\fR(1)\&. May be set to
always,
false
(or
never) or
auto
(or
true), in which case colors are used only when the output is to a terminal\&. Defaults to false\&.
.RE
.PP
color\&.status\&.<slot>
.RS 4
Use customized color for status colorization\&.
<slot>
is one of
header
(the header text of the status message),
added
or
updated
(files which are added but not committed),
changed
(files which are changed but not added in the index),
untracked
(files which are not tracked by Git),
branch
(the current branch),
nobranch
(the color the
\fIno branch\fR
warning is shown in, defaulting to red), or
unmerged
(files which have unmerged changes)\&.
.RE
.PP
color\&.ui
.RS 4
This variable determines the default value for variables such as
color\&.diff
and
color\&.grep
that control the use of color per command family\&. Its scope will expand as more commands learn configuration to set a default for the
\-\-color
option\&. Set it to
false
or
never
if you prefer Git commands not to use color unless enabled explicitly with some other configuration or the
\-\-color
option\&. Set it to
always
if you want all output not intended for machine consumption to use color, to
true
or
auto
(this is the default since Git 1\&.8\&.4) if you want such output to use color when written to the terminal\&.
.RE
.PP
column\&.ui
.RS 4
Specify whether supported commands should output in columns\&. This variable consists of a list of tokens separated by spaces or commas:
.sp
These options control when the feature should be enabled (defaults to
\fInever\fR):
.PP
always
.RS 4
always show in columns
.RE
.PP
never
.RS 4
never show in columns
.RE
.PP
auto
.RS 4
show in columns if the output is to the terminal
.RE
.sp
These options control layout (defaults to
\fIcolumn\fR)\&. Setting any of these implies
\fIalways\fR
if none of
\fIalways\fR,
\fInever\fR, or
\fIauto\fR
are specified\&.
.PP
column
.RS 4
fill columns before rows
.RE
.PP
row
.RS 4
fill rows before columns
.RE
.PP
plain
.RS 4
show in one column
.RE
.sp
Finally, these options can be combined with a layout option (defaults to
\fInodense\fR):
.PP
dense
.RS 4
make unequal size columns to utilize more space
.RE
.PP
nodense
.RS 4
make equal size columns
.RE
.RE
.PP
column\&.branch
.RS 4
Specify whether to output branch listing in
git branch
in columns\&. See
column\&.ui
for details\&.
.RE
.PP
column\&.clean
.RS 4
Specify the layout when list items in
git clean \-i, which always shows files and directories in columns\&. See
column\&.ui
for details\&.
.RE
.PP
column\&.status
.RS 4
Specify whether to output untracked files in
git status
in columns\&. See
column\&.ui
for details\&.
.RE
.PP
column\&.tag
.RS 4
Specify whether to output tag listing in
git tag
in columns\&. See
column\&.ui
for details\&.
.RE
.PP
commit\&.cleanup
.RS 4
This setting overrides the default of the
\-\-cleanup
option in
git commit\&. See
\fBgit-commit\fR(1)
for details\&. Changing the default can be useful when you always want to keep lines that begin with comment character
#
in your log message, in which case you would do
git config commit\&.cleanup whitespace
(note that you will have to remove the help lines that begin with
#
in the commit log template yourself, if you do this)\&.
.RE
.PP
commit\&.gpgSign
.RS 4
A boolean to specify whether all commits should be GPG signed\&. Use of this option when doing operations such as rebase can result in a large number of commits being signed\&. It may be convenient to use an agent to avoid typing your GPG passphrase several times\&.
.RE
.PP
commit\&.status
.RS 4
A boolean to enable/disable inclusion of status information in the commit message template when using an editor to prepare the commit message\&. Defaults to true\&.
.RE
.PP
commit\&.template
.RS 4
Specify a file to use as the template for new commit messages\&. "~/" is expanded to the value of
$HOME
and "~user/" to the specified user\(cqs home directory\&.
.RE
.PP
credential\&.helper
.RS 4
Specify an external helper to be called when a username or password credential is needed; the helper may consult external storage to avoid prompting the user for the credentials\&. See
\fBgitcredentials\fR(7)
for details\&.
.RE
.PP
credential\&.useHttpPath
.RS 4
When acquiring credentials, consider the "path" component of an http or https URL to be important\&. Defaults to false\&. See
\fBgitcredentials\fR(7)
for more information\&.
.RE
.PP
credential\&.username
.RS 4
If no username is set for a network authentication, use this username by default\&. See credential\&.<context>\&.* below, and
\fBgitcredentials\fR(7)\&.
.RE
.PP
credential\&.<url>\&.*
.RS 4
Any of the credential\&.* options above can be applied selectively to some credentials\&. For example "credential\&.https://example\&.com\&.username" would set the default username only for https connections to example\&.com\&. See
\fBgitcredentials\fR(7)
for details on how URLs are matched\&.
.RE
.PP
diff\&.autoRefreshIndex
.RS 4
When using
\fIgit diff\fR
to compare with work tree files, do not consider stat\-only change as changed\&. Instead, silently run
git update\-index \-\-refresh
to update the cached stat information for paths whose contents in the work tree match the contents in the index\&. This option defaults to true\&. Note that this affects only
\fIgit diff\fR
Porcelain, and not lower level
\fIdiff\fR
commands such as
\fIgit diff\-files\fR\&.
.RE
.PP
diff\&.dirstat
.RS 4
A comma separated list of
\-\-dirstat
parameters specifying the default behavior of the
\-\-dirstat
option to
\fBgit-diff\fR(1)` and friends\&. The defaults can be overridden on the command line (using
\-\-dirstat=<param1,param2,\&.\&.\&.>)\&. The fallback defaults (when not changed by
diff\&.dirstat) are
changes,noncumulative,3\&. The following parameters are available:
.PP
changes
.RS 4
Compute the dirstat numbers by counting the lines that have been removed from the source, or added to the destination\&. This ignores the amount of pure code movements within a file\&. In other words, rearranging lines in a file is not counted as much as other changes\&. This is the default behavior when no parameter is given\&.
.RE
.PP
lines
.RS 4
Compute the dirstat numbers by doing the regular line\-based diff analysis, and summing the removed/added line counts\&. (For binary files, count 64\-byte chunks instead, since binary files have no natural concept of lines)\&. This is a more expensive
\-\-dirstat
behavior than the
changes
behavior, but it does count rearranged lines within a file as much as other changes\&. The resulting output is consistent with what you get from the other
\-\-*stat
options\&.
.RE
.PP
files
.RS 4
Compute the dirstat numbers by counting the number of files changed\&. Each changed file counts equally in the dirstat analysis\&. This is the computationally cheapest
\-\-dirstat
behavior, since it does not have to look at the file contents at all\&.
.RE
.PP
cumulative
.RS 4
Count changes in a child directory for the parent directory as well\&. Note that when using
cumulative, the sum of the percentages reported may exceed 100%\&. The default (non\-cumulative) behavior can be specified with the
noncumulative
parameter\&.
.RE
.PP
<limit>
.RS 4
An integer parameter specifies a cut\-off percent (3% by default)\&. Directories contributing less than this percentage of the changes are not shown in the output\&.
.RE
.sp
Example: The following will count changed files, while ignoring directories with less than 10% of the total amount of changed files, and accumulating child directory counts in the parent directories:
files,10,cumulative\&.
.RE
.PP
diff\&.statGraphWidth
.RS 4
Limit the width of the graph part in \-\-stat output\&. If set, applies to all commands generating \-\-stat output except format\-patch\&.
.RE
.PP
diff\&.context
.RS 4
Generate diffs with <n> lines of context instead of the default of 3\&. This value is overridden by the \-U option\&.
.RE
.PP
diff\&.external
.RS 4
If this config variable is set, diff generation is not performed using the internal diff machinery, but using the given command\&. Can be overridden with the \(oqGIT_EXTERNAL_DIFF\(cq environment variable\&. The command is called with parameters as described under "git Diffs" in
\fBgit\fR(1)\&. Note: if you want to use an external diff program only on a subset of your files, you might want to use
\fBgitattributes\fR(5)
instead\&.
.RE
.PP
diff\&.ignoreSubmodules
.RS 4
Sets the default value of \-\-ignore\-submodules\&. Note that this affects only
\fIgit diff\fR
Porcelain, and not lower level
\fIdiff\fR
commands such as
\fIgit diff\-files\fR\&.
\fIgit checkout\fR
also honors this setting when reporting uncommitted changes\&. Setting it to
\fIall\fR
disables the submodule summary normally shown by
\fIgit commit\fR
and
\fIgit status\fR
when
\fIstatus\&.submoduleSummary\fR
is set unless it is overridden by using the \-\-ignore\-submodules command\-line option\&. The
\fIgit submodule\fR
commands are not affected by this setting\&.
.RE
.PP
diff\&.mnemonicPrefix
.RS 4
If set,
\fIgit diff\fR
uses a prefix pair that is different from the standard "a/" and "b/" depending on what is being compared\&. When this configuration is in effect, reverse diff output also swaps the order of the prefixes:
.PP
git diff
.RS 4
compares the (i)ndex and the (w)ork tree;
.RE
.PP
git diff HEAD
.RS 4
compares a (c)ommit and the (w)ork tree;
.RE
.PP
git diff \-\-cached
.RS 4
compares a (c)ommit and the (i)ndex;
.RE
.PP
git diff HEAD:file1 file2
.RS 4
compares an (o)bject and a (w)ork tree entity;
.RE
.PP
git diff \-\-no\-index a b
.RS 4
compares two non\-git things (1) and (2)\&.
.RE
.RE
.PP
diff\&.noprefix
.RS 4
If set,
\fIgit diff\fR
does not show any source or destination prefix\&.
.RE
.PP
diff\&.orderFile
.RS 4
File indicating how to order files within a diff, using one shell glob pattern per line\&. Can be overridden by the
\fI\-O\fR
option to
\fBgit-diff\fR(1)\&.
.RE
.PP
diff\&.renameLimit
.RS 4
The number of files to consider when performing the copy/rename detection; equivalent to the
\fIgit diff\fR
option
\fI\-l\fR\&.
.RE
.PP
diff\&.renames
.RS 4
Tells Git to detect renames\&. If set to any boolean value, it will enable basic rename detection\&. If set to "copies" or "copy", it will detect copies, as well\&.
.RE
.PP
diff\&.suppressBlankEmpty
.RS 4
A boolean to inhibit the standard behavior of printing a space before each empty output line\&. Defaults to false\&.
.RE
.PP
diff\&.submodule
.RS 4
Specify the format in which differences in submodules are shown\&. The "log" format lists the commits in the range like
\fBgit-submodule\fR(1)summary
does\&. The "short" format format just shows the names of the commits at the beginning and end of the range\&. Defaults to short\&.
.RE
.PP
diff\&.wordRegex
.RS 4
A POSIX Extended Regular Expression used to determine what is a "word" when performing word\-by\-word difference calculations\&. Character sequences that match the regular expression are "words", all other characters are
\fBignorable\fR
whitespace\&.
.RE
.PP
diff\&.<driver>\&.command
.RS 4
The custom diff driver command\&. See
\fBgitattributes\fR(5)
for details\&.
.RE
.PP
diff\&.<driver>\&.xfuncname
.RS 4
The regular expression that the diff driver should use to recognize the hunk header\&. A built\-in pattern may also be used\&. See
\fBgitattributes\fR(5)
for details\&.
.RE
.PP
diff\&.<driver>\&.binary
.RS 4
Set this option to true to make the diff driver treat files as binary\&. See
\fBgitattributes\fR(5)
for details\&.
.RE
.PP
diff\&.<driver>\&.textconv
.RS 4
The command that the diff driver should call to generate the text\-converted version of a file\&. The result of the conversion is used to generate a human\-readable diff\&. See
\fBgitattributes\fR(5)
for details\&.
.RE
.PP
diff\&.<driver>\&.wordRegex
.RS 4
The regular expression that the diff driver should use to split words in a line\&. See
\fBgitattributes\fR(5)
for details\&.
.RE
.PP
diff\&.<driver>\&.cachetextconv
.RS 4
Set this option to true to make the diff driver cache the text conversion outputs\&. See
\fBgitattributes\fR(5)
for details\&.
.RE
.PP
diff\&.tool
.RS 4
Controls which diff tool is used by
\fBgit-difftool\fR(1)\&. This variable overrides the value configured in
merge\&.tool\&. The list below shows the valid built\-in values\&. Any other value is treated as a custom diff tool and requires that a corresponding difftool\&.<tool>\&.cmd variable is defined\&.
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
araxis
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
bc
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
bc3
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
codecompare
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
deltawalker
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
diffmerge
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
diffuse
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
ecmerge
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
emerge
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
gvimdiff
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
gvimdiff2
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
gvimdiff3
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
kdiff3
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
kompare
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
meld
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
opendiff
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
p4merge
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
tkdiff
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
vimdiff
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
vimdiff2
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
vimdiff3
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
winmerge
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
xxdiff
.RE
.RE
.PP
diff\&.algorithm
.RS 4
Choose a diff algorithm\&. The variants are as follows:
.PP
default, myers
.RS 4
The basic greedy diff algorithm\&. Currently, this is the default\&.
.RE
.PP
minimal
.RS 4
Spend extra time to make sure the smallest possible diff is produced\&.
.RE
.PP
patience
.RS 4
Use "patience diff" algorithm when generating patches\&.
.RE
.PP
histogram
.RS 4
This algorithm extends the patience algorithm to "support low\-occurrence common elements"\&.
.RE
.RE
.PP
difftool\&.<tool>\&.path
.RS 4
Override the path for the given tool\&. This is useful in case your tool is not in the PATH\&.
.RE
.PP
difftool\&.<tool>\&.cmd
.RS 4
Specify the command to invoke the specified diff tool\&. The specified command is evaluated in shell with the following variables available:
\fILOCAL\fR
is set to the name of the temporary file containing the contents of the diff pre\-image and
\fIREMOTE\fR
is set to the name of the temporary file containing the contents of the diff post\-image\&.
.RE
.PP
difftool\&.prompt
.RS 4
Prompt before each invocation of the diff tool\&.
.RE
.PP
fetch\&.recurseSubmodules
.RS 4
This option can be either set to a boolean value or to
\fIon\-demand\fR\&. Setting it to a boolean changes the behavior of fetch and pull to unconditionally recurse into submodules when set to true or to not recurse at all when set to false\&. When set to
\fIon\-demand\fR
(the default value), fetch and pull will only recurse into a populated submodule when its superproject retrieves a commit that updates the submodule\(cqs reference\&.
.RE
.PP
fetch\&.fsckObjects
.RS 4
If it is set to true, git\-fetch\-pack will check all fetched objects\&. It will abort in the case of a malformed object or a broken link\&. The result of an abort are only dangling objects\&. Defaults to false\&. If not set, the value of
transfer\&.fsckObjects
is used instead\&.
.RE
.PP
fetch\&.unpackLimit
.RS 4
If the number of objects fetched over the Git native transfer is below this limit, then the objects will be unpacked into loose object files\&. However if the number of received objects equals or exceeds this limit then the received pack will be stored as a pack, after adding any missing delta bases\&. Storing the pack from a push can make the push operation complete faster, especially on slow filesystems\&. If not set, the value of
transfer\&.unpackLimit
is used instead\&.
.RE
.PP
fetch\&.prune
.RS 4
If true, fetch will automatically behave as if the
\-\-prune
option was given on the command line\&. See also
remote\&.<name>\&.prune\&.
.RE
.PP
format\&.attach
.RS 4
Enable multipart/mixed attachments as the default for
\fIformat\-patch\fR\&. The value can also be a double quoted string which will enable attachments as the default and set the value as the boundary\&. See the \-\-attach option in
\fBgit-format-patch\fR(1)\&.
.RE
.PP
format\&.numbered
.RS 4
A boolean which can enable or disable sequence numbers in patch subjects\&. It defaults to "auto" which enables it only if there is more than one patch\&. It can be enabled or disabled for all messages by setting it to "true" or "false"\&. See \-\-numbered option in
\fBgit-format-patch\fR(1)\&.
.RE
.PP
format\&.headers
.RS 4
Additional email headers to include in a patch to be submitted by mail\&. See
\fBgit-format-patch\fR(1)\&.
.RE
.PP
format\&.to, format\&.cc
.RS 4
Additional recipients to include in a patch to be submitted by mail\&. See the \-\-to and \-\-cc options in
\fBgit-format-patch\fR(1)\&.
.RE
.PP
format\&.subjectPrefix
.RS 4
The default for format\-patch is to output files with the
\fI[PATCH]\fR
subject prefix\&. Use this variable to change that prefix\&.
.RE
.PP
format\&.signature
.RS 4
The default for format\-patch is to output a signature containing the Git version number\&. Use this variable to change that default\&. Set this variable to the empty string ("") to suppress signature generation\&.
.RE
.PP
format\&.signatureFile
.RS 4
Works just like format\&.signature except the contents of the file specified by this variable will be used as the signature\&.
.RE
.PP
format\&.suffix
.RS 4
The default for format\-patch is to output files with the suffix
\&.patch\&. Use this variable to change that suffix (make sure to include the dot if you want it)\&.
.RE
.PP
format\&.pretty
.RS 4
The default pretty format for log/show/whatchanged command, See
\fBgit-log\fR(1),
\fBgit-show\fR(1),
\fBgit-whatchanged\fR(1)\&.
.RE
.PP
format\&.thread
.RS 4
The default threading style for
\fIgit format\-patch\fR\&. Can be a boolean value, or
shallow
or
deep\&.
shallow
threading makes every mail a reply to the head of the series, where the head is chosen from the cover letter, the
\-\-in\-reply\-to, and the first patch mail, in this order\&.
deep
threading makes every mail a reply to the previous one\&. A true boolean value is the same as
shallow, and a false value disables threading\&.
.RE
.PP
format\&.signOff
.RS 4
A boolean value which lets you enable the
\-s/\-\-signoff
option of format\-patch by default\&.
\fBNote:\fR
Adding the Signed\-off\-by: line to a patch should be a conscious act and means that you certify you have the rights to submit this work under the same open source license\&. Please see the
\fISubmittingPatches\fR
document for further discussion\&.
.RE
.PP
format\&.coverLetter
.RS 4
A boolean that controls whether to generate a cover\-letter when format\-patch is invoked, but in addition can be set to "auto", to generate a cover\-letter only when there\(cqs more than one patch\&.
.RE
.PP
filter\&.<driver>\&.clean
.RS 4
The command which is used to convert the content of a worktree file to a blob upon checkin\&. See
\fBgitattributes\fR(5)
for details\&.
.RE
.PP
filter\&.<driver>\&.smudge
.RS 4
The command which is used to convert the content of a blob object to a worktree file upon checkout\&. See
\fBgitattributes\fR(5)
for details\&.
.RE
.PP
fsck\&.<msg\-id>
.RS 4
Allows overriding the message type (error, warn or ignore) of a specific message ID such as
missingEmail\&.
.sp
For convenience, fsck prefixes the error/warning with the message ID, e\&.g\&. "missingEmail: invalid author/committer line \- missing email" means that setting
fsck\&.missingEmail = ignore
will hide that issue\&.
.sp
This feature is intended to support working with legacy repositories which cannot be repaired without disruptive changes\&.
.RE
.PP
fsck\&.skipList
.RS 4
The path to a sorted list of object names (i\&.e\&. one SHA\-1 per line) that are known to be broken in a non\-fatal way and should be ignored\&. This feature is useful when an established project should be accepted despite early commits containing errors that can be safely ignored such as invalid committer email addresses\&. Note: corrupt objects cannot be skipped with this setting\&.
.RE
.PP
gc\&.aggressiveDepth
.RS 4
The depth parameter used in the delta compression algorithm used by
\fIgit gc \-\-aggressive\fR\&. This defaults to 250\&.
.RE
.PP
gc\&.aggressiveWindow
.RS 4
The window size parameter used in the delta compression algorithm used by
\fIgit gc \-\-aggressive\fR\&. This defaults to 250\&.
.RE
.PP
gc\&.auto
.RS 4
When there are approximately more than this many loose objects in the repository,
git gc \-\-auto
will pack them\&. Some Porcelain commands use this command to perform a light\-weight garbage collection from time to time\&. The default value is 6700\&. Setting this to 0 disables it\&.
.RE
.PP
gc\&.autoPackLimit
.RS 4
When there are more than this many packs that are not marked with
*\&.keep
file in the repository,
git gc \-\-auto
consolidates them into one larger pack\&. The default value is 50\&. Setting this to 0 disables it\&.
.RE
.PP
gc\&.autoDetach
.RS 4
Make
git gc \-\-auto
return immediately and run in background if the system supports it\&. Default is true\&.
.RE
.PP
gc\&.packRefs
.RS 4
Running
git pack\-refs
in a repository renders it unclonable by Git versions prior to 1\&.5\&.1\&.2 over dumb transports such as HTTP\&. This variable determines whether
\fIgit gc\fR
runs
git pack\-refs\&. This can be set to
notbare
to enable it within all non\-bare repos or it can be set to a boolean value\&. The default is
true\&.
.RE
.PP
gc\&.pruneExpire
.RS 4
When
\fIgit gc\fR
is run, it will call
\fIprune \-\-expire 2\&.weeks\&.ago\fR\&. Override the grace period with this config variable\&. The value "now" may be used to disable this grace period and always prune unreachable objects immediately, or "never" may be used to suppress pruning\&.
.RE
.PP
gc\&.worktreePruneExpire
.RS 4
When
\fIgit gc\fR
is run, it calls
\fIgit worktree prune \-\-expire 3\&.months\&.ago\fR\&. This config variable can be used to set a different grace period\&. The value "now" may be used to disable the grace period and prune $GIT_DIR/worktrees immediately, or "never" may be used to suppress pruning\&.
.RE
.PP
gc\&.reflogExpire, gc\&.<pattern>\&.reflogExpire
.RS 4
\fIgit reflog expire\fR
removes reflog entries older than this time; defaults to 90 days\&. The value "now" expires all entries immediately, and "never" suppresses expiration altogether\&. With "<pattern>" (e\&.g\&. "refs/stash") in the middle the setting applies only to the refs that match the <pattern>\&.
.RE
.PP
gc\&.reflogExpireUnreachable, gc\&.<ref>\&.reflogExpireUnreachable
.RS 4
\fIgit reflog expire\fR
removes reflog entries older than this time and are not reachable from the current tip; defaults to 30 days\&. The value "now" expires all entries immediately, and "never" suppresses expiration altogether\&. With "<pattern>" (e\&.g\&. "refs/stash") in the middle, the setting applies only to the refs that match the <pattern>\&.
.RE
.PP
gc\&.rerereResolved
.RS 4
Records of conflicted merge you resolved earlier are kept for this many days when
\fIgit rerere gc\fR
is run\&. The default is 60 days\&. See
\fBgit-rerere\fR(1)\&.
.RE
.PP
gc\&.rerereUnresolved
.RS 4
Records of conflicted merge you have not resolved are kept for this many days when
\fIgit rerere gc\fR
is run\&. The default is 15 days\&. See
\fBgit-rerere\fR(1)\&.
.RE
.PP
gitcvs\&.commitMsgAnnotation
.RS 4
Append this string to each commit message\&. Set to empty string to disable this feature\&. Defaults to "via git\-CVS emulator"\&.
.RE
.PP
gitcvs\&.enabled
.RS 4
Whether the CVS server interface is enabled for this repository\&. See
\fBgit-cvsserver\fR(1)\&.
.RE
.PP
gitcvs\&.logFile
.RS 4
Path to a log file where the CVS server interface well\&... logs various stuff\&. See
\fBgit-cvsserver\fR(1)\&.
.RE
.PP
gitcvs\&.usecrlfattr
.RS 4
If true, the server will look up the end\-of\-line conversion attributes for files to determine the
\fI\-k\fR
modes to use\&. If the attributes force Git to treat a file as text, the
\fI\-k\fR
mode will be left blank so CVS clients will treat it as text\&. If they suppress text conversion, the file will be set with
\fI\-kb\fR
mode, which suppresses any newline munging the client might otherwise do\&. If the attributes do not allow the file type to be determined, then
\fIgitcvs\&.allBinary\fR
is used\&. See
\fBgitattributes\fR(5)\&.
.RE
.PP
gitcvs\&.allBinary
.RS 4
This is used if
\fIgitcvs\&.usecrlfattr\fR
does not resolve the correct
\fI\-kb\fR
mode to use\&. If true, all unresolved files are sent to the client in mode
\fI\-kb\fR\&. This causes the client to treat them as binary files, which suppresses any newline munging it otherwise might do\&. Alternatively, if it is set to "guess", then the contents of the file are examined to decide if it is binary, similar to
\fIcore\&.autocrlf\fR\&.
.RE
.PP
gitcvs\&.dbName
.RS 4
Database used by git\-cvsserver to cache revision information derived from the Git repository\&. The exact meaning depends on the used database driver, for SQLite (which is the default driver) this is a filename\&. Supports variable substitution (see
\fBgit-cvsserver\fR(1)
for details)\&. May not contain semicolons (;)\&. Default:
\fI%Ggitcvs\&.%m\&.sqlite\fR
.RE
.PP
gitcvs\&.dbDriver
.RS 4
Used Perl DBI driver\&. You can specify any available driver for this here, but it might not work\&. git\-cvsserver is tested with
\fIDBD::SQLite\fR, reported to work with
\fIDBD::Pg\fR, and reported
\fBnot\fR
to work with
\fIDBD::mysql\fR\&. Experimental feature\&. May not contain double colons (:)\&. Default:
\fISQLite\fR\&. See
\fBgit-cvsserver\fR(1)\&.
.RE
.PP
gitcvs\&.dbUser, gitcvs\&.dbPass
.RS 4
Database user and password\&. Only useful if setting
\fIgitcvs\&.dbDriver\fR, since SQLite has no concept of database users and/or passwords\&.
\fIgitcvs\&.dbUser\fR
supports variable substitution (see
\fBgit-cvsserver\fR(1)
for details)\&.
.RE
.PP
gitcvs\&.dbTableNamePrefix
.RS 4
Database table name prefix\&. Prepended to the names of any database tables used, allowing a single database to be used for several repositories\&. Supports variable substitution (see
\fBgit-cvsserver\fR(1)
for details)\&. Any non\-alphabetic characters will be replaced with underscores\&.
.RE
.sp
All gitcvs variables except for \fIgitcvs\&.usecrlfattr\fR and \fIgitcvs\&.allBinary\fR can also be specified as \fIgitcvs\&.<access_method>\&.<varname>\fR (where \fIaccess_method\fR is one of "ext" and "pserver") to make them apply only for the given access method\&.
.PP
gitweb\&.category, gitweb\&.description, gitweb\&.owner, gitweb\&.url
.RS 4
See
\fBgitweb\fR(1)
for description\&.
.RE
.PP
gitweb\&.avatar, gitweb\&.blame, gitweb\&.grep, gitweb\&.highlight, gitweb\&.patches, gitweb\&.pickaxe, gitweb\&.remote_heads, gitweb\&.showSizes, gitweb\&.snapshot
.RS 4
See
\fBgitweb.conf\fR(5)
for description\&.
.RE
.PP
grep\&.lineNumber
.RS 4
If set to true, enable
\fI\-n\fR
option by default\&.
.RE
.PP
grep\&.patternType
.RS 4
Set the default matching behavior\&. Using a value of
\fIbasic\fR,
\fIextended\fR,
\fIfixed\fR, or
\fIperl\fR
will enable the
\fI\-\-basic\-regexp\fR,
\fI\-\-extended\-regexp\fR,
\fI\-\-fixed\-strings\fR, or
\fI\-\-perl\-regexp\fR
option accordingly, while the value
\fIdefault\fR
will return to the default matching behavior\&.
.RE
.PP
grep\&.extendedRegexp
.RS 4
If set to true, enable
\fI\-\-extended\-regexp\fR
option by default\&. This option is ignored when the
\fIgrep\&.patternType\fR
option is set to a value other than
\fIdefault\fR\&.
.RE
.PP
gpg\&.program
.RS 4
Use this custom program instead of "gpg" found on $PATH when making or verifying a PGP signature\&. The program must support the same command\-line interface as GPG, namely, to verify a detached signature, "gpg \-\-verify $file \- <$signature" is run, and the program is expected to signal a good signature by exiting with code 0, and to generate an ASCII\-armored detached signature, the standard input of "gpg \-bsau $key" is fed with the contents to be signed, and the program is expected to send the result to its standard output\&.
.RE
.PP
gui\&.commitMsgWidth
.RS 4
Defines how wide the commit message window is in the
\fBgit-gui\fR(1)\&. "75" is the default\&.
.RE
.PP
gui\&.diffContext
.RS 4
Specifies how many context lines should be used in calls to diff made by the
\fBgit-gui\fR(1)\&. The default is "5"\&.
.RE
.PP
gui\&.displayUntracked
.RS 4
Determines if
\fB:git-gui\fR(1)
shows untracked files in the file list\&. The default is "true"\&.
.RE
.PP
gui\&.encoding
.RS 4
Specifies the default encoding to use for displaying of file contents in
\fBgit-gui\fR(1)
and
\fBgitk\fR(1)\&. It can be overridden by setting the
\fIencoding\fR
attribute for relevant files (see
\fBgitattributes\fR(5))\&. If this option is not set, the tools default to the locale encoding\&.
.RE
.PP
gui\&.matchTrackingBranch
.RS 4
Determines if new branches created with
\fBgit-gui\fR(1)
should default to tracking remote branches with matching names or not\&. Default: "false"\&.
.RE
.PP
gui\&.newBranchTemplate
.RS 4
Is used as suggested name when creating new branches using the
\fBgit-gui\fR(1)\&.
.RE
.PP
gui\&.pruneDuringFetch
.RS 4
"true" if
\fBgit-gui\fR(1)
should prune remote\-tracking branches when performing a fetch\&. The default value is "false"\&.
.RE
.PP
gui\&.trustmtime
.RS 4
Determines if
\fBgit-gui\fR(1)
should trust the file modification timestamp or not\&. By default the timestamps are not trusted\&.
.RE
.PP
gui\&.spellingDictionary
.RS 4
Specifies the dictionary used for spell checking commit messages in the
\fBgit-gui\fR(1)\&. When set to "none" spell checking is turned off\&.
.RE
.PP
gui\&.fastCopyBlame
.RS 4
If true,
\fIgit gui blame\fR
uses
\-C
instead of
\-C \-C
for original location detection\&. It makes blame significantly faster on huge repositories at the expense of less thorough copy detection\&.
.RE
.PP
gui\&.copyBlameThreshold
.RS 4
Specifies the threshold to use in
\fIgit gui blame\fR
original location detection, measured in alphanumeric characters\&. See the
\fBgit-blame\fR(1)
manual for more information on copy detection\&.
.RE
.PP
gui\&.blamehistoryctx
.RS 4
Specifies the radius of history context in days to show in
\fBgitk\fR(1)
for the selected commit, when the
Show History Context
menu item is invoked from
\fIgit gui blame\fR\&. If this variable is set to zero, the whole history is shown\&.
.RE
.PP
guitool\&.<name>\&.cmd
.RS 4
Specifies the shell command line to execute when the corresponding item of the
\fBgit-gui\fR(1)Tools
menu is invoked\&. This option is mandatory for every tool\&. The command is executed from the root of the working directory, and in the environment it receives the name of the tool as
\fIGIT_GUITOOL\fR, the name of the currently selected file as
\fIFILENAME\fR, and the name of the current branch as
\fICUR_BRANCH\fR
(if the head is detached,
\fICUR_BRANCH\fR
is empty)\&.
.RE
.PP
guitool\&.<name>\&.needsFile
.RS 4
Run the tool only if a diff is selected in the GUI\&. It guarantees that
\fIFILENAME\fR
is not empty\&.
.RE
.PP
guitool\&.<name>\&.noConsole
.RS 4
Run the command silently, without creating a window to display its output\&.
.RE
.PP
guitool\&.<name>\&.noRescan
.RS 4
Don\(cqt rescan the working directory for changes after the tool finishes execution\&.
.RE
.PP
guitool\&.<name>\&.confirm
.RS 4
Show a confirmation dialog before actually running the tool\&.
.RE
.PP
guitool\&.<name>\&.argPrompt
.RS 4
Request a string argument from the user, and pass it to the tool through the
\fIARGS\fR
environment variable\&. Since requesting an argument implies confirmation, the
\fIconfirm\fR
option has no effect if this is enabled\&. If the option is set to
\fItrue\fR,
\fIyes\fR, or
\fI1\fR, the dialog uses a built\-in generic prompt; otherwise the exact value of the variable is used\&.
.RE
.PP
guitool\&.<name>\&.revPrompt
.RS 4
Request a single valid revision from the user, and set the
\fIREVISION\fR
environment variable\&. In other aspects this option is similar to
\fIargPrompt\fR, and can be used together with it\&.
.RE
.PP
guitool\&.<name>\&.revUnmerged
.RS 4
Show only unmerged branches in the
\fIrevPrompt\fR
subdialog\&. This is useful for tools similar to merge or rebase, but not for things like checkout or reset\&.
.RE
.PP
guitool\&.<name>\&.title
.RS 4
Specifies the title to use for the prompt dialog\&. The default is the tool name\&.
.RE
.PP
guitool\&.<name>\&.prompt
.RS 4
Specifies the general prompt string to display at the top of the dialog, before subsections for
\fIargPrompt\fR
and
\fIrevPrompt\fR\&. The default value includes the actual command\&.
.RE
.PP
help\&.browser
.RS 4
Specify the browser that will be used to display help in the
\fIweb\fR
format\&. See
\fBgit-help\fR(1)\&.
.RE
.PP
help\&.format
.RS 4
Override the default help format used by
\fBgit-help\fR(1)\&. Values
\fIman\fR,
\fIinfo\fR,
\fIweb\fR
and
\fIhtml\fR
are supported\&.
\fIman\fR
is the default\&.
\fIweb\fR
and
\fIhtml\fR
are the same\&.
.RE
.PP
help\&.autoCorrect
.RS 4
Automatically correct and execute mistyped commands after waiting for the given number of deciseconds (0\&.1 sec)\&. If more than one command can be deduced from the entered text, nothing will be executed\&. If the value of this option is negative, the corrected command will be executed immediately\&. If the value is 0 \- the command will be just shown but not executed\&. This is the default\&.
.RE
.PP
help\&.htmlPath
.RS 4
Specify the path where the HTML documentation resides\&. File system paths and URLs are supported\&. HTML pages will be prefixed with this path when help is displayed in the
\fIweb\fR
format\&. This defaults to the documentation path of your Git installation\&.
.RE
.PP
http\&.proxy
.RS 4
Override the HTTP proxy, normally configured using the
\fIhttp_proxy\fR,
\fIhttps_proxy\fR, and
\fIall_proxy\fR
environment variables (see
curl(1))\&. This can be overridden on a per\-remote basis; see remote\&.<name>\&.proxy
.RE
.PP
http\&.cookieFile
.RS 4
File containing previously stored cookie lines which should be used in the Git http session, if they match the server\&. The file format of the file to read cookies from should be plain HTTP headers or the Netscape/Mozilla cookie file format (see
\fBcurl\fR(1))\&. NOTE that the file specified with http\&.cookieFile is only used as input unless http\&.saveCookies is set\&.
.RE
.PP
http\&.saveCookies
.RS 4
If set, store cookies received during requests to the file specified by http\&.cookieFile\&. Has no effect if http\&.cookieFile is unset\&.
.RE
.PP
http\&.sslCipherList
.RS 4
A list of SSL ciphers to use when negotiating an SSL connection\&. The available ciphers depend on whether libcurl was built against NSS or OpenSSL and the particular configuration of the crypto library in use\&. Internally this sets the
\fICURLOPT_SSL_CIPHER_LIST\fR
option; see the libcurl documentation for more details on the format of this list\&.
.sp
Can be overridden by the
\fIGIT_SSL_CIPHER_LIST\fR
environment variable\&. To force git to use libcurl\(cqs default cipher list and ignore any explicit http\&.sslCipherList option, set
\fIGIT_SSL_CIPHER_LIST\fR
to the empty string\&.
.RE
.PP
http\&.sslVerify
.RS 4
Whether to verify the SSL certificate when fetching or pushing over HTTPS\&. Can be overridden by the
\fIGIT_SSL_NO_VERIFY\fR
environment variable\&.
.RE
.PP
http\&.sslCert
.RS 4
File containing the SSL certificate when fetching or pushing over HTTPS\&. Can be overridden by the
\fIGIT_SSL_CERT\fR
environment variable\&.
.RE
.PP
http\&.sslKey
.RS 4
File containing the SSL private key when fetching or pushing over HTTPS\&. Can be overridden by the
\fIGIT_SSL_KEY\fR
environment variable\&.
.RE
.PP
http\&.sslCertPasswordProtected
.RS 4
Enable Git\(cqs password prompt for the SSL certificate\&. Otherwise OpenSSL will prompt the user, possibly many times, if the certificate or private key is encrypted\&. Can be overridden by the
\fIGIT_SSL_CERT_PASSWORD_PROTECTED\fR
environment variable\&.
.RE
.PP
http\&.sslCAInfo
.RS 4
File containing the certificates to verify the peer with when fetching or pushing over HTTPS\&. Can be overridden by the
\fIGIT_SSL_CAINFO\fR
environment variable\&.
.RE
.PP
http\&.sslCAPath
.RS 4
Path containing files with the CA certificates to verify the peer with when fetching or pushing over HTTPS\&. Can be overridden by the
\fIGIT_SSL_CAPATH\fR
environment variable\&.
.RE
.PP
http\&.sslTry
.RS 4
Attempt to use AUTH SSL/TLS and encrypted data transfers when connecting via regular FTP protocol\&. This might be needed if the FTP server requires it for security reasons or you wish to connect securely whenever remote FTP server supports it\&. Default is false since it might trigger certificate verification errors on misconfigured servers\&.
.RE
.PP
http\&.maxRequests
.RS 4
How many HTTP requests to launch in parallel\&. Can be overridden by the
\fIGIT_HTTP_MAX_REQUESTS\fR
environment variable\&. Default is 5\&.
.RE
.PP
http\&.minSessions
.RS 4
The number of curl sessions (counted across slots) to be kept across requests\&. They will not be ended with curl_easy_cleanup() until http_cleanup() is invoked\&. If USE_CURL_MULTI is not defined, this value will be capped at 1\&. Defaults to 1\&.
.RE
.PP
http\&.postBuffer
.RS 4
Maximum size in bytes of the buffer used by smart HTTP transports when POSTing data to the remote system\&. For requests larger than this buffer size, HTTP/1\&.1 and Transfer\-Encoding: chunked is used to avoid creating a massive pack file locally\&. Default is 1 MiB, which is sufficient for most requests\&.
.RE
.PP
http\&.lowSpeedLimit, http\&.lowSpeedTime
.RS 4
If the HTTP transfer speed is less than
\fIhttp\&.lowSpeedLimit\fR
for longer than
\fIhttp\&.lowSpeedTime\fR
seconds, the transfer is aborted\&. Can be overridden by the
\fIGIT_HTTP_LOW_SPEED_LIMIT\fR
and
\fIGIT_HTTP_LOW_SPEED_TIME\fR
environment variables\&.
.RE
.PP
http\&.noEPSV
.RS 4
A boolean which disables using of EPSV ftp command by curl\&. This can helpful with some "poor" ftp servers which don\(cqt support EPSV mode\&. Can be overridden by the
\fIGIT_CURL_FTP_NO_EPSV\fR
environment variable\&. Default is false (curl will use EPSV)\&.
.RE
.PP
http\&.userAgent
.RS 4
The HTTP USER_AGENT string presented to an HTTP server\&. The default value represents the version of the client Git such as git/1\&.7\&.1\&. This option allows you to override this value to a more common value such as Mozilla/4\&.0\&. This may be necessary, for instance, if connecting through a firewall that restricts HTTP connections to a set of common USER_AGENT strings (but not including those like git/1\&.7\&.1)\&. Can be overridden by the
\fIGIT_HTTP_USER_AGENT\fR
environment variable\&.
.RE
.PP
http\&.<url>\&.*
.RS 4
Any of the http\&.* options above can be applied selectively to some URLs\&. For a config key to match a URL, each element of the config key is compared to that of the URL, in the following order:
.sp
.RS 4
.ie n \{\
\h'-04' 1.\h'+01'\c
.\}
.el \{\
.sp -1
.IP "  1." 4.2
.\}
Scheme (e\&.g\&.,
https
in
https://example\&.com/)\&. This field must match exactly between the config key and the URL\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04' 2.\h'+01'\c
.\}
.el \{\
.sp -1
.IP "  2." 4.2
.\}
Host/domain name (e\&.g\&.,
example\&.com
in
https://example\&.com/)\&. This field must match exactly between the config key and the URL\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04' 3.\h'+01'\c
.\}
.el \{\
.sp -1
.IP "  3." 4.2
.\}
Port number (e\&.g\&.,
8080
in
http://example\&.com:8080/)\&. This field must match exactly between the config key and the URL\&. Omitted port numbers are automatically converted to the correct default for the scheme before matching\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04' 4.\h'+01'\c
.\}
.el \{\
.sp -1
.IP "  4." 4.2
.\}
Path (e\&.g\&.,
repo\&.git
in
https://example\&.com/repo\&.git)\&. The path field of the config key must match the path field of the URL either exactly or as a prefix of slash\-delimited path elements\&. This means a config key with path
foo/
matches URL path
foo/bar\&. A prefix can only match on a slash (/) boundary\&. Longer matches take precedence (so a config key with path
foo/bar
is a better match to URL path
foo/bar
than a config key with just path
foo/)\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04' 5.\h'+01'\c
.\}
.el \{\
.sp -1
.IP "  5." 4.2
.\}
User name (e\&.g\&.,
user
in
https://user@example\&.com/repo\&.git)\&. If the config key has a user name it must match the user name in the URL exactly\&. If the config key does not have a user name, that config key will match a URL with any user name (including none), but at a lower precedence than a config key with a user name\&.
.RE
.sp
The list above is ordered by decreasing precedence; a URL that matches a config key\(cqs path is preferred to one that matches its user name\&. For example, if the URL is
https://user@example\&.com/foo/bar
a config key match of
https://example\&.com/foo
will be preferred over a config key match of
https://user@example\&.com\&.
.sp
All URLs are normalized before attempting any matching (the password part, if embedded in the URL, is always ignored for matching purposes) so that equivalent URLs that are simply spelled differently will match properly\&. Environment variable settings always override any matches\&. The URLs that are matched against are those given directly to Git commands\&. This means any URLs visited as a result of a redirection do not participate in matching\&.
.RE
.PP
i18n\&.commitEncoding
.RS 4
Character encoding the commit messages are stored in; Git itself does not care per se, but this information is necessary e\&.g\&. when importing commits from emails or in the gitk graphical history browser (and possibly at other places in the future or in other porcelains)\&. See e\&.g\&.
\fBgit-mailinfo\fR(1)\&. Defaults to
\fIutf\-8\fR\&.
.RE
.PP
i18n\&.logOutputEncoding
.RS 4
Character encoding the commit messages are converted to when running
\fIgit log\fR
and friends\&.
.RE
.PP
imap
.RS 4
The configuration variables in the
\fIimap\fR
section are described in
\fBgit-imap-send\fR(1)\&.
.RE
.PP
index\&.version
.RS 4
Specify the version with which new index files should be initialized\&. This does not affect existing repositories\&.
.RE
.PP
init\&.templateDir
.RS 4
Specify the directory from which templates will be copied\&. (See the "TEMPLATE DIRECTORY" section of
\fBgit-init\fR(1)\&.)
.RE
.PP
instaweb\&.browser
.RS 4
Specify the program that will be used to browse your working repository in gitweb\&. See
\fBgit-instaweb\fR(1)\&.
.RE
.PP
instaweb\&.httpd
.RS 4
The HTTP daemon command\-line to start gitweb on your working repository\&. See
\fBgit-instaweb\fR(1)\&.
.RE
.PP
instaweb\&.local
.RS 4
If true the web server started by
\fBgit-instaweb\fR(1)
will be bound to the local IP (127\&.0\&.0\&.1)\&.
.RE
.PP
instaweb\&.modulePath
.RS 4
The default module path for
\fBgit-instaweb\fR(1)
to use instead of /usr/lib/apache2/modules\&. Only used if httpd is Apache\&.
.RE
.PP
instaweb\&.port
.RS 4
The port number to bind the gitweb httpd to\&. See
\fBgit-instaweb\fR(1)\&.
.RE
.PP
interactive\&.singleKey
.RS 4
In interactive commands, allow the user to provide one\-letter input with a single key (i\&.e\&., without hitting enter)\&. Currently this is used by the
\-\-patch
mode of
\fBgit-add\fR(1),
\fBgit-checkout\fR(1),
\fBgit-commit\fR(1),
\fBgit-reset\fR(1), and
\fBgit-stash\fR(1)\&. Note that this setting is silently ignored if portable keystroke input is not available; requires the Perl module Term::ReadKey\&.
.RE
.PP
log\&.abbrevCommit
.RS 4
If true, makes
\fBgit-log\fR(1),
\fBgit-show\fR(1), and
\fBgit-whatchanged\fR(1)
assume
\-\-abbrev\-commit\&. You may override this option with
\-\-no\-abbrev\-commit\&.
.RE
.PP
log\&.date
.RS 4
Set the default date\-time mode for the
\fIlog\fR
command\&. Setting a value for log\&.date is similar to using
\fIgit log\fR\(aqs
\-\-date
option\&. Possible values are
relative,
local,
default,
iso,
rfc, and
short; see
\fBgit-log\fR(1)
for details\&.
.RE
.PP
log\&.decorate
.RS 4
Print out the ref names of any commits that are shown by the log command\&. If
\fIshort\fR
is specified, the ref name prefixes
\fIrefs/heads/\fR,
\fIrefs/tags/\fR
and
\fIrefs/remotes/\fR
will not be printed\&. If
\fIfull\fR
is specified, the full ref name (including prefix) will be printed\&. This is the same as the log commands
\fI\-\-decorate\fR
option\&.
.RE
.PP
log\&.showRoot
.RS 4
If true, the initial commit will be shown as a big creation event\&. This is equivalent to a diff against an empty tree\&. Tools like
\fBgit-log\fR(1)
or
\fBgit-whatchanged\fR(1), which normally hide the root commit will now show it\&. True by default\&.
.RE
.PP
log\&.mailmap
.RS 4
If true, makes
\fBgit-log\fR(1),
\fBgit-show\fR(1), and
\fBgit-whatchanged\fR(1)
assume
\-\-use\-mailmap\&.
.RE
.PP
mailinfo\&.scissors
.RS 4
If true, makes
\fBgit-mailinfo\fR(1)
(and therefore
\fBgit-am\fR(1)) act by default as if the \-\-scissors option was provided on the command\-line\&. When active, this features removes everything from the message body before a scissors line (i\&.e\&. consisting mainly of ">8", "8<" and "\-")\&.
.RE
.PP
mailmap\&.file
.RS 4
The location of an augmenting mailmap file\&. The default mailmap, located in the root of the repository, is loaded first, then the mailmap file pointed to by this variable\&. The location of the mailmap file may be in a repository subdirectory, or somewhere outside of the repository itself\&. See
\fBgit-shortlog\fR(1)
and
\fBgit-blame\fR(1)\&.
.RE
.PP
mailmap\&.blob
.RS 4
Like
mailmap\&.file, but consider the value as a reference to a blob in the repository\&. If both
mailmap\&.file
and
mailmap\&.blob
are given, both are parsed, with entries from
mailmap\&.file
taking precedence\&. In a bare repository, this defaults to
HEAD:\&.mailmap\&. In a non\-bare repository, it defaults to empty\&.
.RE
.PP
man\&.viewer
.RS 4
Specify the programs that may be used to display help in the
\fIman\fR
format\&. See
\fBgit-help\fR(1)\&.
.RE
.PP
man\&.<tool>\&.cmd
.RS 4
Specify the command to invoke the specified man viewer\&. The specified command is evaluated in shell with the man page passed as argument\&. (See
\fBgit-help\fR(1)\&.)
.RE
.PP
man\&.<tool>\&.path
.RS 4
Override the path for the given tool that may be used to display help in the
\fIman\fR
format\&. See
\fBgit-help\fR(1)\&.
.RE
.PP
merge\&.conflictStyle
.RS 4
Specify the style in which conflicted hunks are written out to working tree files upon merge\&. The default is "merge", which shows a
<<<<<<<
conflict marker, changes made by one side, a
=======
marker, changes made by the other side, and then a
>>>>>>>
marker\&. An alternate style, "diff3", adds a
|||||||
marker and the original text before the
=======
marker\&.
.RE
.PP
merge\&.defaultToUpstream
.RS 4
If merge is called without any commit argument, merge the upstream branches configured for the current branch by using their last observed values stored in their remote\-tracking branches\&. The values of the
branch\&.<current branch>\&.merge
that name the branches at the remote named by
branch\&.<current branch>\&.remote
are consulted, and then they are mapped via
remote\&.<remote>\&.fetch
to their corresponding remote\-tracking branches, and the tips of these tracking branches are merged\&.
.RE
.PP
merge\&.ff
.RS 4
By default, Git does not create an extra merge commit when merging a commit that is a descendant of the current commit\&. Instead, the tip of the current branch is fast\-forwarded\&. When set to
false, this variable tells Git to create an extra merge commit in such a case (equivalent to giving the
\-\-no\-ff
option from the command line)\&. When set to
only, only such fast\-forward merges are allowed (equivalent to giving the
\-\-ff\-only
option from the command line)\&.
.RE
.PP
merge\&.branchdesc
.RS 4
In addition to branch names, populate the log message with the branch description text associated with them\&. Defaults to false\&.
.RE
.PP
merge\&.log
.RS 4
In addition to branch names, populate the log message with at most the specified number of one\-line descriptions from the actual commits that are being merged\&. Defaults to false, and true is a synonym for 20\&.
.RE
.PP
merge\&.renameLimit
.RS 4
The number of files to consider when performing rename detection during a merge; if not specified, defaults to the value of diff\&.renameLimit\&.
.RE
.PP
merge\&.renormalize
.RS 4
Tell Git that canonical representation of files in the repository has changed over time (e\&.g\&. earlier commits record text files with CRLF line endings, but recent ones use LF line endings)\&. In such a repository, Git can convert the data recorded in commits to a canonical form before performing a merge to reduce unnecessary conflicts\&. For more information, see section "Merging branches with differing checkin/checkout attributes" in
\fBgitattributes\fR(5)\&.
.RE
.PP
merge\&.stat
.RS 4
Whether to print the diffstat between ORIG_HEAD and the merge result at the end of the merge\&. True by default\&.
.RE
.PP
merge\&.tool
.RS 4
Controls which merge tool is used by
\fBgit-mergetool\fR(1)\&. The list below shows the valid built\-in values\&. Any other value is treated as a custom merge tool and requires that a corresponding mergetool\&.<tool>\&.cmd variable is defined\&.
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
araxis
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
bc
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
bc3
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
codecompare
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
deltawalker
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
diffmerge
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
diffuse
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
ecmerge
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
emerge
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
gvimdiff
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
gvimdiff2
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
gvimdiff3
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
kdiff3
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
meld
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
opendiff
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
p4merge
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
tkdiff
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
tortoisemerge
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
vimdiff
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
vimdiff2
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
vimdiff3
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
winmerge
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
xxdiff
.RE
.RE
.PP
merge\&.verbosity
.RS 4
Controls the amount of output shown by the recursive merge strategy\&. Level 0 outputs nothing except a final error message if conflicts were detected\&. Level 1 outputs only conflicts, 2 outputs conflicts and file changes\&. Level 5 and above outputs debugging information\&. The default is level 2\&. Can be overridden by the
\fIGIT_MERGE_VERBOSITY\fR
environment variable\&.
.RE
.PP
merge\&.<driver>\&.name
.RS 4
Defines a human\-readable name for a custom low\-level merge driver\&. See
\fBgitattributes\fR(5)
for details\&.
.RE
.PP
merge\&.<driver>\&.driver
.RS 4
Defines the command that implements a custom low\-level merge driver\&. See
\fBgitattributes\fR(5)
for details\&.
.RE
.PP
merge\&.<driver>\&.recursive
.RS 4
Names a low\-level merge driver to be used when performing an internal merge between common ancestors\&. See
\fBgitattributes\fR(5)
for details\&.
.RE
.PP
mergetool\&.<tool>\&.path
.RS 4
Override the path for the given tool\&. This is useful in case your tool is not in the PATH\&.
.RE
.PP
mergetool\&.<tool>\&.cmd
.RS 4
Specify the command to invoke the specified merge tool\&. The specified command is evaluated in shell with the following variables available:
\fIBASE\fR
is the name of a temporary file containing the common base of the files to be merged, if available;
\fILOCAL\fR
is the name of a temporary file containing the contents of the file on the current branch;
\fIREMOTE\fR
is the name of a temporary file containing the contents of the file from the branch being merged;
\fIMERGED\fR
contains the name of the file to which the merge tool should write the results of a successful merge\&.
.RE
.PP
mergetool\&.<tool>\&.trustExitCode
.RS 4
For a custom merge command, specify whether the exit code of the merge command can be used to determine whether the merge was successful\&. If this is not set to true then the merge target file timestamp is checked and the merge assumed to have been successful if the file has been updated, otherwise the user is prompted to indicate the success of the merge\&.
.RE
.PP
mergetool\&.meld\&.hasOutput
.RS 4
Older versions of
meld
do not support the
\-\-output
option\&. Git will attempt to detect whether
meld
supports
\-\-output
by inspecting the output of
meld \-\-help\&. Configuring
mergetool\&.meld\&.hasOutput
will make Git skip these checks and use the configured value instead\&. Setting
mergetool\&.meld\&.hasOutput
to
true
tells Git to unconditionally use the
\-\-output
option, and
false
avoids using
\-\-output\&.
.RE
.PP
mergetool\&.keepBackup
.RS 4
After performing a merge, the original file with conflict markers can be saved as a file with a
\&.orig
extension\&. If this variable is set to
false
then this file is not preserved\&. Defaults to
true
(i\&.e\&. keep the backup files)\&.
.RE
.PP
mergetool\&.keepTemporaries
.RS 4
When invoking a custom merge tool, Git uses a set of temporary files to pass to the tool\&. If the tool returns an error and this variable is set to
true, then these temporary files will be preserved, otherwise they will be removed after the tool has exited\&. Defaults to
false\&.
.RE
.PP
mergetool\&.writeToTemp
.RS 4
Git writes temporary
\fIBASE\fR,
\fILOCAL\fR, and
\fIREMOTE\fR
versions of conflicting files in the worktree by default\&. Git will attempt to use a temporary directory for these files when set
true\&. Defaults to
false\&.
.RE
.PP
mergetool\&.prompt
.RS 4
Prompt before each invocation of the merge resolution program\&.
.RE
.PP
notes\&.displayRef
.RS 4
The (fully qualified) refname from which to show notes when showing commit messages\&. The value of this variable can be set to a glob, in which case notes from all matching refs will be shown\&. You may also specify this configuration variable several times\&. A warning will be issued for refs that do not exist, but a glob that does not match any refs is silently ignored\&.
.sp
This setting can be overridden with the
GIT_NOTES_DISPLAY_REF
environment variable, which must be a colon separated list of refs or globs\&.
.sp
The effective value of "core\&.notesRef" (possibly overridden by GIT_NOTES_REF) is also implicitly added to the list of refs to be displayed\&.
.RE
.PP
notes\&.rewrite\&.<command>
.RS 4
When rewriting commits with <command> (currently
amend
or
rebase) and this variable is set to
true, Git automatically copies your notes from the original to the rewritten commit\&. Defaults to
true, but see "notes\&.rewriteRef" below\&.
.RE
.PP
notes\&.rewriteMode
.RS 4
When copying notes during a rewrite (see the "notes\&.rewrite\&.<command>" option), determines what to do if the target commit already has a note\&. Must be one of
overwrite,
concatenate, or
ignore\&. Defaults to
concatenate\&.
.sp
This setting can be overridden with the
GIT_NOTES_REWRITE_MODE
environment variable\&.
.RE
.PP
notes\&.rewriteRef
.RS 4
When copying notes during a rewrite, specifies the (fully qualified) ref whose notes should be copied\&. The ref may be a glob, in which case notes in all matching refs will be copied\&. You may also specify this configuration several times\&.
.sp
Does not have a default value; you must configure this variable to enable note rewriting\&. Set it to
refs/notes/commits
to enable rewriting for the default commit notes\&.
.sp
This setting can be overridden with the
GIT_NOTES_REWRITE_REF
environment variable, which must be a colon separated list of refs or globs\&.
.RE
.PP
pack\&.window
.RS 4
The size of the window used by
\fBgit-pack-objects\fR(1)
when no window size is given on the command line\&. Defaults to 10\&.
.RE
.PP
pack\&.depth
.RS 4
The maximum delta depth used by
\fBgit-pack-objects\fR(1)
when no maximum depth is given on the command line\&. Defaults to 50\&.
.RE
.PP
pack\&.windowMemory
.RS 4
The maximum size of memory that is consumed by each thread in
\fBgit-pack-objects\fR(1)
for pack window memory when no limit is given on the command line\&. The value can be suffixed with "k", "m", or "g"\&. When left unconfigured (or set explicitly to 0), there will be no limit\&.
.RE
.PP
pack\&.compression
.RS 4
An integer \-1\&.\&.9, indicating the compression level for objects in a pack file\&. \-1 is the zlib default\&. 0 means no compression, and 1\&.\&.9 are various speed/size tradeoffs, 9 being slowest\&. If not set, defaults to core\&.compression\&. If that is not set, defaults to \-1, the zlib default, which is "a default compromise between speed and compression (currently equivalent to level 6)\&."
.sp
Note that changing the compression level will not automatically recompress all existing objects\&. You can force recompression by passing the \-F option to
\fBgit-repack\fR(1)\&.
.RE
.PP
pack\&.deltaCacheSize
.RS 4
The maximum memory in bytes used for caching deltas in
\fBgit-pack-objects\fR(1)
before writing them out to a pack\&. This cache is used to speed up the writing object phase by not having to recompute the final delta result once the best match for all objects is found\&. Repacking large repositories on machines which are tight with memory might be badly impacted by this though, especially if this cache pushes the system into swapping\&. A value of 0 means no limit\&. The smallest size of 1 byte may be used to virtually disable this cache\&. Defaults to 256 MiB\&.
.RE
.PP
pack\&.deltaCacheLimit
.RS 4
The maximum size of a delta, that is cached in
\fBgit-pack-objects\fR(1)\&. This cache is used to speed up the writing object phase by not having to recompute the final delta result once the best match for all objects is found\&. Defaults to 1000\&.
.RE
.PP
pack\&.threads
.RS 4
Specifies the number of threads to spawn when searching for best delta matches\&. This requires that
\fBgit-pack-objects\fR(1)
be compiled with pthreads otherwise this option is ignored with a warning\&. This is meant to reduce packing time on multiprocessor machines\&. The required amount of memory for the delta search window is however multiplied by the number of threads\&. Specifying 0 will cause Git to auto\-detect the number of CPU\(cqs and set the number of threads accordingly\&.
.RE
.PP
pack\&.indexVersion
.RS 4
Specify the default pack index version\&. Valid values are 1 for legacy pack index used by Git versions prior to 1\&.5\&.2, and 2 for the new pack index with capabilities for packs larger than 4 GB as well as proper protection against the repacking of corrupted packs\&. Version 2 is the default\&. Note that version 2 is enforced and this config option ignored whenever the corresponding pack is larger than 2 GB\&.
.sp
If you have an old Git that does not understand the version 2
*\&.idx
file, cloning or fetching over a non native protocol (e\&.g\&. "http" and "rsync") that will copy both
*\&.pack
file and corresponding
*\&.idx
file from the other side may give you a repository that cannot be accessed with your older version of Git\&. If the
*\&.pack
file is smaller than 2 GB, however, you can use
\fBgit-index-pack\fR(1)
on the *\&.pack file to regenerate the
*\&.idx
file\&.
.RE
.PP
pack\&.packSizeLimit
.RS 4
The maximum size of a pack\&. This setting only affects packing to a file when repacking, i\&.e\&. the git:// protocol is unaffected\&. It can be overridden by the
\-\-max\-pack\-size
option of
\fBgit-repack\fR(1)\&. The minimum size allowed is limited to 1 MiB\&. The default is unlimited\&. Common unit suffixes of
\fIk\fR,
\fIm\fR, or
\fIg\fR
are supported\&.
.RE
.PP
pack\&.useBitmaps
.RS 4
When true, git will use pack bitmaps (if available) when packing to stdout (e\&.g\&., during the server side of a fetch)\&. Defaults to true\&. You should not generally need to turn this off unless you are debugging pack bitmaps\&.
.RE
.PP
pack\&.writeBitmaps (deprecated)
.RS 4
This is a deprecated synonym for
repack\&.writeBitmaps\&.
.RE
.PP
pack\&.writeBitmapHashCache
.RS 4
When true, git will include a "hash cache" section in the bitmap index (if one is written)\&. This cache can be used to feed git\(cqs delta heuristics, potentially leading to better deltas between bitmapped and non\-bitmapped objects (e\&.g\&., when serving a fetch between an older, bitmapped pack and objects that have been pushed since the last gc)\&. The downside is that it consumes 4 bytes per object of disk space, and that JGit\(cqs bitmap implementation does not understand it, causing it to complain if Git and JGit are used on the same repository\&. Defaults to false\&.
.RE
.PP
pager\&.<cmd>
.RS 4
If the value is boolean, turns on or off pagination of the output of a particular Git subcommand when writing to a tty\&. Otherwise, turns on pagination for the subcommand using the pager specified by the value of
pager\&.<cmd>\&. If
\-\-paginate
or
\-\-no\-pager
is specified on the command line, it takes precedence over this option\&. To disable pagination for all commands, set
core\&.pager
or
GIT_PAGER
to
cat\&.
.RE
.PP
pretty\&.<name>
.RS 4
Alias for a \-\-pretty= format string, as specified in
\fBgit-log\fR(1)\&. Any aliases defined here can be used just as the built\-in pretty formats could\&. For example, running
git config pretty\&.changelog "format:* %H %s"
would cause the invocation
git log \-\-pretty=changelog
to be equivalent to running
git log "\-\-pretty=format:* %H %s"\&. Note that an alias with the same name as a built\-in format will be silently ignored\&.
.RE
.PP
pull\&.ff
.RS 4
By default, Git does not create an extra merge commit when merging a commit that is a descendant of the current commit\&. Instead, the tip of the current branch is fast\-forwarded\&. When set to
false, this variable tells Git to create an extra merge commit in such a case (equivalent to giving the
\-\-no\-ff
option from the command line)\&. When set to
only, only such fast\-forward merges are allowed (equivalent to giving the
\-\-ff\-only
option from the command line)\&. This setting overrides
merge\&.ff
when pulling\&.
.RE
.PP
pull\&.rebase
.RS 4
When true, rebase branches on top of the fetched branch, instead of merging the default branch from the default remote when "git pull" is run\&. See "branch\&.<name>\&.rebase" for setting this on a per\-branch basis\&.
.sp
.if n \{\
.RS 4
.\}
.nf
When preserve, also pass `\-\-preserve\-merges` along to \(aqgit rebase\(aq
so that locally committed merge commits will not be flattened
by running \(aqgit pull\(aq\&.
.fi
.if n \{\
.RE
.\}
.sp
\fBNOTE\fR: this is a possibly dangerous operation; do
\fBnot\fR
use it unless you understand the implications (see
\fBgit-rebase\fR(1)
for details)\&.
.RE
.PP
pull\&.octopus
.RS 4
The default merge strategy to use when pulling multiple branches at once\&.
.RE
.PP
pull\&.twohead
.RS 4
The default merge strategy to use when pulling a single branch\&.
.RE
.PP
push\&.default
.RS 4
Defines the action
git push
should take if no refspec is explicitly given\&. Different values are well\-suited for specific workflows; for instance, in a purely central workflow (i\&.e\&. the fetch source is equal to the push destination),
upstream
is probably what you want\&. Possible values are:
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
nothing
\- do not push anything (error out) unless a refspec is explicitly given\&. This is primarily meant for people who want to avoid mistakes by always being explicit\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
current
\- push the current branch to update a branch with the same name on the receiving end\&. Works in both central and non\-central workflows\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
upstream
\- push the current branch back to the branch whose changes are usually integrated into the current branch (which is called
@{upstream})\&. This mode only makes sense if you are pushing to the same repository you would normally pull from (i\&.e\&. central workflow)\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
simple
\- in centralized workflow, work like
upstream
with an added safety to refuse to push if the upstream branch\(cqs name is different from the local one\&.
.sp
When pushing to a remote that is different from the remote you normally pull from, work as
current\&. This is the safest option and is suited for beginners\&.
.sp
This mode has become the default in Git 2\&.0\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
matching
\- push all branches having the same name on both ends\&. This makes the repository you are pushing to remember the set of branches that will be pushed out (e\&.g\&. if you always push
\fImaint\fR
and
\fImaster\fR
there and no other branches, the repository you push to will have these two branches, and your local
\fImaint\fR
and
\fImaster\fR
will be pushed there)\&.
.sp
To use this mode effectively, you have to make sure
\fIall\fR
the branches you would push out are ready to be pushed out before running
\fIgit push\fR, as the whole point of this mode is to allow you to push all of the branches in one go\&. If you usually finish work on only one branch and push out the result, while other branches are unfinished, this mode is not for you\&. Also this mode is not suitable for pushing into a shared central repository, as other people may add new branches there, or update the tip of existing branches outside your control\&.
.sp
This used to be the default, but not since Git 2\&.0 (simple
is the new default)\&.
.RE
.RE
.PP
push\&.followTags
.RS 4
If set to true enable
\fI\-\-follow\-tags\fR
option by default\&. You may override this configuration at time of push by specifying
\fI\-\-no\-follow\-tags\fR\&.
.RE
.PP
rebase\&.stat
.RS 4
Whether to show a diffstat of what changed upstream since the last rebase\&. False by default\&.
.RE
.PP
rebase\&.autoSquash
.RS 4
If set to true enable
\fI\-\-autosquash\fR
option by default\&.
.RE
.PP
rebase\&.autoStash
.RS 4
When set to true, automatically create a temporary stash before the operation begins, and apply it after the operation ends\&. This means that you can run rebase on a dirty worktree\&. However, use with care: the final stash application after a successful rebase might result in non\-trivial conflicts\&. Defaults to false\&.
.RE
.PP
rebase\&.missingCommitsCheck
.RS 4
If set to "warn", git rebase \-i will print a warning if some commits are removed (e\&.g\&. a line was deleted), however the rebase will still proceed\&. If set to "error", it will print the previous warning and stop the rebase,
\fIgit rebase \-\-edit\-todo\fR
can then be used to correct the error\&. If set to "ignore", no checking is done\&. To drop a commit without warning or error, use the
drop
command in the todo\-list\&. Defaults to "ignore"\&.
.RE
.sp
rebase\&.instructionFormat A format string, as specified in \fBgit-log\fR(1), to be used for the instruction list during an interactive rebase\&. The format will automatically have the long commit hash prepended to the format\&.
.PP
receive\&.advertiseAtomic
.RS 4
By default, git\-receive\-pack will advertise the atomic push capability to its clients\&. If you don\(cqt want to this capability to be advertised, set this variable to false\&.
.RE
.PP
receive\&.autogc
.RS 4
By default, git\-receive\-pack will run "git\-gc \-\-auto" after receiving data from git\-push and updating refs\&. You can stop it by setting this variable to false\&.
.RE
.PP
receive\&.certNonceSeed
.RS 4
By setting this variable to a string,
git receive\-pack
will accept a
git push \-\-signed
and verifies it by using a "nonce" protected by HMAC using this string as a secret key\&.
.RE
.PP
receive\&.certNonceSlop
.RS 4
When a
git push \-\-signed
sent a push certificate with a "nonce" that was issued by a receive\-pack serving the same repository within this many seconds, export the "nonce" found in the certificate to
GIT_PUSH_CERT_NONCE
to the hooks (instead of what the receive\-pack asked the sending side to include)\&. This may allow writing checks in
pre\-receive
and
post\-receive
a bit easier\&. Instead of checking
GIT_PUSH_CERT_NONCE_SLOP
environment variable that records by how many seconds the nonce is stale to decide if they want to accept the certificate, they only can check
GIT_PUSH_CERT_NONCE_STATUS
is
OK\&.
.RE
.PP
receive\&.fsckObjects
.RS 4
If it is set to true, git\-receive\-pack will check all received objects\&. It will abort in the case of a malformed object or a broken link\&. The result of an abort are only dangling objects\&. Defaults to false\&. If not set, the value of
transfer\&.fsckObjects
is used instead\&.
.RE
.PP
receive\&.fsck\&.<msg\-id>
.RS 4
When
receive\&.fsckObjects
is set to true, errors can be switched to warnings and vice versa by configuring the
receive\&.fsck\&.<msg\-id>
setting where the
<msg\-id>
is the fsck message ID and the value is one of
error,
warn
or
ignore\&. For convenience, fsck prefixes the error/warning with the message ID, e\&.g\&. "missingEmail: invalid author/committer line \- missing email" means that setting
receive\&.fsck\&.missingEmail = ignore
will hide that issue\&.
.sp
This feature is intended to support working with legacy repositories which would not pass pushing when
receive\&.fsckObjects = true, allowing the host to accept repositories with certain known issues but still catch other issues\&.
.RE
.PP
receive\&.fsck\&.skipList
.RS 4
The path to a sorted list of object names (i\&.e\&. one SHA\-1 per line) that are known to be broken in a non\-fatal way and should be ignored\&. This feature is useful when an established project should be accepted despite early commits containing errors that can be safely ignored such as invalid committer email addresses\&. Note: corrupt objects cannot be skipped with this setting\&.
.RE
.PP
receive\&.unpackLimit
.RS 4
If the number of objects received in a push is below this limit then the objects will be unpacked into loose object files\&. However if the number of received objects equals or exceeds this limit then the received pack will be stored as a pack, after adding any missing delta bases\&. Storing the pack from a push can make the push operation complete faster, especially on slow filesystems\&. If not set, the value of
transfer\&.unpackLimit
is used instead\&.
.RE
.PP
receive\&.denyDeletes
.RS 4
If set to true, git\-receive\-pack will deny a ref update that deletes the ref\&. Use this to prevent such a ref deletion via a push\&.
.RE
.PP
receive\&.denyDeleteCurrent
.RS 4
If set to true, git\-receive\-pack will deny a ref update that deletes the currently checked out branch of a non\-bare repository\&.
.RE
.PP
receive\&.denyCurrentBranch
.RS 4
If set to true or "refuse", git\-receive\-pack will deny a ref update to the currently checked out branch of a non\-bare repository\&. Such a push is potentially dangerous because it brings the HEAD out of sync with the index and working tree\&. If set to "warn", print a warning of such a push to stderr, but allow the push to proceed\&. If set to false or "ignore", allow such pushes with no message\&. Defaults to "refuse"\&.
.sp
Another option is "updateInstead" which will update the working tree if pushing into the current branch\&. This option is intended for synchronizing working directories when one side is not easily accessible via interactive ssh (e\&.g\&. a live web site, hence the requirement that the working directory be clean)\&. This mode also comes in handy when developing inside a VM to test and fix code on different Operating Systems\&.
.sp
By default, "updateInstead" will refuse the push if the working tree or the index have any difference from the HEAD, but the
push\-to\-checkout
hook can be used to customize this\&. See
\fBgithooks\fR(5)\&.
.RE
.PP
receive\&.denyNonFastForwards
.RS 4
If set to true, git\-receive\-pack will deny a ref update which is not a fast\-forward\&. Use this to prevent such an update via a push, even if that push is forced\&. This configuration variable is set when initializing a shared repository\&.
.RE
.PP
receive\&.hideRefs
.RS 4
This variable is the same as
transfer\&.hideRefs, but applies only to
receive\-pack
(and so affects pushes, but not fetches)\&. An attempt to update or delete a hidden ref by
git push
is rejected\&.
.RE
.PP
receive\&.updateServerInfo
.RS 4
If set to true, git\-receive\-pack will run git\-update\-server\-info after receiving data from git\-push and updating refs\&.
.RE
.PP
receive\&.shallowUpdate
.RS 4
If set to true, \&.git/shallow can be updated when new refs require new shallow roots\&. Otherwise those refs are rejected\&.
.RE
.PP
remote\&.pushDefault
.RS 4
The remote to push to by default\&. Overrides
branch\&.<name>\&.remote
for all branches, and is overridden by
branch\&.<name>\&.pushRemote
for specific branches\&.
.RE
.PP
remote\&.<name>\&.url
.RS 4
The URL of a remote repository\&. See
\fBgit-fetch\fR(1)
or
\fBgit-push\fR(1)\&.
.RE
.PP
remote\&.<name>\&.pushurl
.RS 4
The push URL of a remote repository\&. See
\fBgit-push\fR(1)\&.
.RE
.PP
remote\&.<name>\&.proxy
.RS 4
For remotes that require curl (http, https and ftp), the URL to the proxy to use for that remote\&. Set to the empty string to disable proxying for that remote\&.
.RE
.PP
remote\&.<name>\&.fetch
.RS 4
The default set of "refspec" for
\fBgit-fetch\fR(1)\&. See
\fBgit-fetch\fR(1)\&.
.RE
.PP
remote\&.<name>\&.push
.RS 4
The default set of "refspec" for
\fBgit-push\fR(1)\&. See
\fBgit-push\fR(1)\&.
.RE
.PP
remote\&.<name>\&.mirror
.RS 4
If true, pushing to this remote will automatically behave as if the
\-\-mirror
option was given on the command line\&.
.RE
.PP
remote\&.<name>\&.skipDefaultUpdate
.RS 4
If true, this remote will be skipped by default when updating using
\fBgit-fetch\fR(1)
or the
update
subcommand of
\fBgit-remote\fR(1)\&.
.RE
.PP
remote\&.<name>\&.skipFetchAll
.RS 4
If true, this remote will be skipped by default when updating using
\fBgit-fetch\fR(1)
or the
update
subcommand of
\fBgit-remote\fR(1)\&.
.RE
.PP
remote\&.<name>\&.receivepack
.RS 4
The default program to execute on the remote side when pushing\&. See option \-\-receive\-pack of
\fBgit-push\fR(1)\&.
.RE
.PP
remote\&.<name>\&.uploadpack
.RS 4
The default program to execute on the remote side when fetching\&. See option \-\-upload\-pack of
\fBgit-fetch-pack\fR(1)\&.
.RE
.PP
remote\&.<name>\&.tagOpt
.RS 4
Setting this value to \-\-no\-tags disables automatic tag following when fetching from remote <name>\&. Setting it to \-\-tags will fetch every tag from remote <name>, even if they are not reachable from remote branch heads\&. Passing these flags directly to
\fBgit-fetch\fR(1)
can override this setting\&. See options \-\-tags and \-\-no\-tags of
\fBgit-fetch\fR(1)\&.
.RE
.PP
remote\&.<name>\&.vcs
.RS 4
Setting this to a value <vcs> will cause Git to interact with the remote with the git\-remote\-<vcs> helper\&.
.RE
.PP
remote\&.<name>\&.prune
.RS 4
When set to true, fetching from this remote by default will also remove any remote\-tracking references that no longer exist on the remote (as if the
\-\-prune
option was given on the command line)\&. Overrides
fetch\&.prune
settings, if any\&.
.RE
.PP
remotes\&.<group>
.RS 4
The list of remotes which are fetched by "git remote update <group>"\&. See
\fBgit-remote\fR(1)\&.
.RE
.PP
repack\&.useDeltaBaseOffset
.RS 4
By default,
\fBgit-repack\fR(1)
creates packs that use delta\-base offset\&. If you need to share your repository with Git older than version 1\&.4\&.4, either directly or via a dumb protocol such as http, then you need to set this option to "false" and repack\&. Access from old Git versions over the native protocol are unaffected by this option\&.
.RE
.PP
repack\&.packKeptObjects
.RS 4
If set to true, makes
git repack
act as if
\-\-pack\-kept\-objects
was passed\&. See
\fBgit-repack\fR(1)
for details\&. Defaults to
false
normally, but
true
if a bitmap index is being written (either via
\-\-write\-bitmap\-index
or
repack\&.writeBitmaps)\&.
.RE
.PP
repack\&.writeBitmaps
.RS 4
When true, git will write a bitmap index when packing all objects to disk (e\&.g\&., when
git repack \-a
is run)\&. This index can speed up the "counting objects" phase of subsequent packs created for clones and fetches, at the cost of some disk space and extra time spent on the initial repack\&. Defaults to false\&.
.RE
.PP
rerere\&.autoUpdate
.RS 4
When set to true,
git\-rerere
updates the index with the resulting contents after it cleanly resolves conflicts using previously recorded resolution\&. Defaults to false\&.
.RE
.PP
rerere\&.enabled
.RS 4
Activate recording of resolved conflicts, so that identical conflict hunks can be resolved automatically, should they be encountered again\&. By default,
\fBgit-rerere\fR(1)
is enabled if there is an
rr\-cache
directory under the
$GIT_DIR, e\&.g\&. if "rerere" was previously used in the repository\&.
.RE
.PP
sendemail\&.identity
.RS 4
A configuration identity\&. When given, causes values in the
\fIsendemail\&.<identity>\fR
subsection to take precedence over values in the
\fIsendemail\fR
section\&. The default identity is the value of
\fIsendemail\&.identity\fR\&.
.RE
.PP
sendemail\&.smtpEncryption
.RS 4
See
\fBgit-send-email\fR(1)
for description\&. Note that this setting is not subject to the
\fIidentity\fR
mechanism\&.
.RE
.PP
sendemail\&.smtpssl (deprecated)
.RS 4
Deprecated alias for
\fIsendemail\&.smtpEncryption = ssl\fR\&.
.RE
.PP
sendemail\&.smtpsslcertpath
.RS 4
Path to ca\-certificates (either a directory or a single file)\&. Set it to an empty string to disable certificate verification\&.
.RE
.PP
sendemail\&.<identity>\&.*
.RS 4
Identity\-specific versions of the
\fIsendemail\&.*\fR
parameters found below, taking precedence over those when the this identity is selected, through command\-line or
\fIsendemail\&.identity\fR\&.
.RE
.PP
sendemail\&.aliasesFile, sendemail\&.aliasFileType, sendemail\&.annotate, sendemail\&.bcc, sendemail\&.cc, sendemail\&.ccCmd, sendemail\&.chainReplyTo, sendemail\&.confirm, sendemail\&.envelopeSender, sendemail\&.from, sendemail\&.multiEdit, sendemail\&.signedoffbycc, sendemail\&.smtpPass, sendemail\&.suppresscc, sendemail\&.suppressFrom, sendemail\&.to, sendemail\&.smtpDomain, sendemail\&.smtpServer, sendemail\&.smtpServerPort, sendemail\&.smtpServerOption, sendemail\&.smtpUser, sendemail\&.thread, sendemail\&.transferEncoding, sendemail\&.validate, sendemail\&.xmailer
.RS 4
See
\fBgit-send-email\fR(1)
for description\&.
.RE
.PP
sendemail\&.signedoffcc (deprecated)
.RS 4
Deprecated alias for
\fIsendemail\&.signedoffbycc\fR\&.
.RE
.PP
showbranch\&.default
.RS 4
The default set of branches for
\fBgit-show-branch\fR(1)\&. See
\fBgit-show-branch\fR(1)\&.
.RE
.PP
status\&.relativePaths
.RS 4
By default,
\fBgit-status\fR(1)
shows paths relative to the current directory\&. Setting this variable to
false
shows paths relative to the repository root (this was the default for Git prior to v1\&.5\&.4)\&.
.RE
.PP
status\&.short
.RS 4
Set to true to enable \-\-short by default in
\fBgit-status\fR(1)\&. The option \-\-no\-short takes precedence over this variable\&.
.RE
.PP
status\&.branch
.RS 4
Set to true to enable \-\-branch by default in
\fBgit-status\fR(1)\&. The option \-\-no\-branch takes precedence over this variable\&.
.RE
.PP
status\&.displayCommentPrefix
.RS 4
If set to true,
\fBgit-status\fR(1)
will insert a comment prefix before each output line (starting with
core\&.commentChar, i\&.e\&.
#
by default)\&. This was the behavior of
\fBgit-status\fR(1)
in Git 1\&.8\&.4 and previous\&. Defaults to false\&.
.RE
.PP
status\&.showUntrackedFiles
.RS 4
By default,
\fBgit-status\fR(1)
and
\fBgit-commit\fR(1)
show files which are not currently tracked by Git\&. Directories which contain only untracked files, are shown with the directory name only\&. Showing untracked files means that Git needs to lstat() all the files in the whole repository, which might be slow on some systems\&. So, this variable controls how the commands displays the untracked files\&. Possible values are:
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
no
\- Show no untracked files\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
normal
\- Show untracked files and directories\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
all
\- Show also individual files in untracked directories\&.
.RE
.sp
If this variable is not specified, it defaults to
\fInormal\fR\&. This variable can be overridden with the \-u|\-\-untracked\-files option of
\fBgit-status\fR(1)
and
\fBgit-commit\fR(1)\&.
.RE
.PP
status\&.submoduleSummary
.RS 4
Defaults to false\&. If this is set to a non zero number or true (identical to \-1 or an unlimited number), the submodule summary will be enabled and a summary of commits for modified submodules will be shown (see \-\-summary\-limit option of
\fBgit-submodule\fR(1))\&. Please note that the summary output command will be suppressed for all submodules when
diff\&.ignoreSubmodules
is set to
\fIall\fR
or only for those submodules where
submodule\&.<name>\&.ignore=all\&. The only exception to that rule is that status and commit will show staged submodule changes\&. To also view the summary for ignored submodules you can either use the \-\-ignore\-submodules=dirty command\-line option or the
\fIgit submodule summary\fR
command, which shows a similar output but does not honor these settings\&.
.RE
.PP
submodule\&.<name>\&.path, submodule\&.<name>\&.url
.RS 4
The path within this project and URL for a submodule\&. These variables are initially populated by
\fIgit submodule init\fR\&. See
\fBgit-submodule\fR(1)
and
\fBgitmodules\fR(5)
for details\&.
.RE
.PP
submodule\&.<name>\&.update
.RS 4
The default update procedure for a submodule\&. This variable is populated by
git submodule init
from the
\fBgitmodules\fR(5)
file\&. See description of
\fIupdate\fR
command in
\fBgit-submodule\fR(1)\&.
.RE
.PP
submodule\&.<name>\&.branch
.RS 4
The remote branch name for a submodule, used by
git submodule update \-\-remote\&. Set this option to override the value found in the
\&.gitmodules
file\&. See
\fBgit-submodule\fR(1)
and
\fBgitmodules\fR(5)
for details\&.
.RE
.PP
submodule\&.<name>\&.fetchRecurseSubmodules
.RS 4
This option can be used to control recursive fetching of this submodule\&. It can be overridden by using the \-\-[no\-]recurse\-submodules command\-line option to "git fetch" and "git pull"\&. This setting will override that from in the
\fBgitmodules\fR(5)
file\&.
.RE
.PP
submodule\&.<name>\&.ignore
.RS 4
Defines under what circumstances "git status" and the diff family show a submodule as modified\&. When set to "all", it will never be considered modified (but it will nonetheless show up in the output of status and commit when it has been staged), "dirty" will ignore all changes to the submodules work tree and takes only differences between the HEAD of the submodule and the commit recorded in the superproject into account\&. "untracked" will additionally let submodules with modified tracked files in their work tree show up\&. Using "none" (the default when this option is not set) also shows submodules that have untracked files in their work tree as changed\&. This setting overrides any setting made in \&.gitmodules for this submodule, both settings can be overridden on the command line by using the "\-\-ignore\-submodules" option\&. The
\fIgit submodule\fR
commands are not affected by this setting\&.
.RE
.PP
tag\&.sort
.RS 4
This variable controls the sort ordering of tags when displayed by
\fBgit-tag\fR(1)\&. Without the "\-\-sort=<value>" option provided, the value of this variable will be used as the default\&.
.RE
.PP
tar\&.umask
.RS 4
This variable can be used to restrict the permission bits of tar archive entries\&. The default is 0002, which turns off the world write bit\&. The special value "user" indicates that the archiving user\(cqs umask will be used instead\&. See umask(2) and
\fBgit-archive\fR(1)\&.
.RE
.PP
transfer\&.fsckObjects
.RS 4
When
fetch\&.fsckObjects
or
receive\&.fsckObjects
are not set, the value of this variable is used instead\&. Defaults to false\&.
.RE
.PP
transfer\&.hideRefs
.RS 4
String(s)
receive\-pack
and
upload\-pack
use to decide which refs to omit from their initial advertisements\&. Use more than one definition to specify multiple prefix strings\&. A ref that is under the hierarchies listed in the value of this variable is excluded, and is hidden when responding to
git push
or
git fetch\&. See
receive\&.hideRefs
and
uploadpack\&.hideRefs
for program\-specific versions of this config\&.
.sp
You may also include a
!
in front of the ref name to negate the entry, explicitly exposing it, even if an earlier entry marked it as hidden\&. If you have multiple hideRefs values, later entries override earlier ones (and entries in more\-specific config files override less\-specific ones)\&.
.RE
.PP
transfer\&.unpackLimit
.RS 4
When
fetch\&.unpackLimit
or
receive\&.unpackLimit
are not set, the value of this variable is used instead\&. The default value is 100\&.
.RE
.PP
uploadarchive\&.allowUnreachable
.RS 4
If true, allow clients to use
git archive \-\-remote
to request any tree, whether reachable from the ref tips or not\&. See the discussion in the
SECURITY
section of
\fBgit-upload-archive\fR(1)
for more details\&. Defaults to
false\&.
.RE
.PP
uploadpack\&.hideRefs
.RS 4
This variable is the same as
transfer\&.hideRefs, but applies only to
upload\-pack
(and so affects only fetches, not pushes)\&. An attempt to fetch a hidden ref by
git fetch
will fail\&. See also
uploadpack\&.allowTipSHA1InWant\&.
.RE
.PP
uploadpack\&.allowTipSHA1InWant
.RS 4
When
uploadpack\&.hideRefs
is in effect, allow
upload\-pack
to accept a fetch request that asks for an object at the tip of a hidden ref (by default, such a request is rejected)\&. see also
uploadpack\&.hideRefs\&.
.RE
.PP
uploadpack\&.allowReachableSHA1InWant
.RS 4
Allow
upload\-pack
to accept a fetch request that asks for an object that is reachable from any ref tip\&. However, note that calculating object reachability is computationally expensive\&. Defaults to
false\&.
.RE
.PP
uploadpack\&.keepAlive
.RS 4
When
upload\-pack
has started
pack\-objects, there may be a quiet period while
pack\-objects
prepares the pack\&. Normally it would output progress information, but if
\-\-quiet
was used for the fetch,
pack\-objects
will output nothing at all until the pack data begins\&. Some clients and networks may consider the server to be hung and give up\&. Setting this option instructs
upload\-pack
to send an empty keepalive packet every
uploadpack\&.keepAlive
seconds\&. Setting this option to 0 disables keepalive packets entirely\&. The default is 5 seconds\&.
.RE
.PP
url\&.<base>\&.insteadOf
.RS 4
Any URL that starts with this value will be rewritten to start, instead, with <base>\&. In cases where some site serves a large number of repositories, and serves them with multiple access methods, and some users need to use different access methods, this feature allows people to specify any of the equivalent URLs and have Git automatically rewrite the URL to the best alternative for the particular user, even for a never\-before\-seen repository on the site\&. When more than one insteadOf strings match a given URL, the longest match is used\&.
.RE
.PP
url\&.<base>\&.pushInsteadOf
.RS 4
Any URL that starts with this value will not be pushed to; instead, it will be rewritten to start with <base>, and the resulting URL will be pushed to\&. In cases where some site serves a large number of repositories, and serves them with multiple access methods, some of which do not allow push, this feature allows people to specify a pull\-only URL and have Git automatically use an appropriate URL to push, even for a never\-before\-seen repository on the site\&. When more than one pushInsteadOf strings match a given URL, the longest match is used\&. If a remote has an explicit pushurl, Git will ignore this setting for that remote\&.
.RE
.PP
user\&.email
.RS 4
Your email address to be recorded in any newly created commits\&. Can be overridden by the
\fIGIT_AUTHOR_EMAIL\fR,
\fIGIT_COMMITTER_EMAIL\fR, and
\fIEMAIL\fR
environment variables\&. See
\fBgit-commit-tree\fR(1)\&.
.RE
.PP
user\&.name
.RS 4
Your full name to be recorded in any newly created commits\&. Can be overridden by the
\fIGIT_AUTHOR_NAME\fR
and
\fIGIT_COMMITTER_NAME\fR
environment variables\&. See
\fBgit-commit-tree\fR(1)\&.
.RE
.PP
user\&.signingKey
.RS 4
If
\fBgit-tag\fR(1)
or
\fBgit-commit\fR(1)
is not selecting the key you want it to automatically when creating a signed tag or commit, you can override the default selection with this variable\&. This option is passed unchanged to gpg\(cqs \-\-local\-user parameter, so you may specify a key using any method that gpg supports\&.
.RE
.PP
versionsort\&.prereleaseSuffix
.RS 4
When version sort is used in
\fBgit-tag\fR(1), prerelease tags (e\&.g\&. "1\&.0\-rc1") may appear after the main release "1\&.0"\&. By specifying the suffix "\-rc" in this variable, "1\&.0\-rc1" will appear before "1\&.0"\&.
.sp
This variable can be specified multiple times, once per suffix\&. The order of suffixes in the config file determines the sorting order (e\&.g\&. if "\-pre" appears before "\-rc" in the config file then 1\&.0\-preXX is sorted before 1\&.0\-rcXX)\&. The sorting order between different suffixes is undefined if they are in multiple config files\&.
.RE
.PP
web\&.browser
.RS 4
Specify a web browser that may be used by some commands\&. Currently only
\fBgit-instaweb\fR(1)
and
\fBgit-help\fR(1)
may use it\&.
.RE
.SH "GIT"
.sp
Part of the \fBgit\fR(1) suite
